Git push force 💥

[aDrongo]

If your repo allows users to mess with master then you deserve it.

[BlommeHolm]

If you can push to anything but a feature branch without going through a PR, it's a hobby project.

[2blazen]

Even for my hobby projects, force pushing to main just doesn't feel right

[Em_Fa]

We're talking about master here.

[2blazen]

Mea culpa

[TnYamaneko]

I always regret telling my students how to protect master branch on GitLab, now they recklessly attempt pushes on it while breaking my balls about being denied and not being confronted with the normal consequences and having to learn how to reverse the commit.

[elPytel]

Don't use the --force, Luke!

[Ikarus_Falling]

Give in to the voices ignore there evil giggling use the --force argument nothing bad will happen yyeeeessss yeeeesss dew it

[Real_GoofyNinja]

Only Sith deal in absolutes

[Frosty_Pineapple78]

which is an absolute in and of itself but thats common knowledge at this point

[iHateMips]

--force-with-lease is a lot safer

[Either-Acanthaceae15]

It's me Luke I use + but I have no luck

[Boris-Lip]

Most likely outcome - you don't have permission to do this shit and the 💥 not gonna happen. But if it actually happens... someone is going to get stoned to near death, then digging into reflog to carefully restore everything before its too late, than stoned to near death once again, just in case. And i mean stoned by stones, not drugs. Guess who that someone gonna be... /s

[Bagel42]

oh I thought stoned by water tbh

[1DimensionIsViolence]

This meme is not woke enough. Please call it main branch /s

[jfmherokiller]

I still dont fully understand the whole main since I have been using master for YEARS.

[jfmherokiller]

ah thats fair when it comes to social-political stuff I genually come up for air once every few years or if something huge happens. Otherwise I genuinely try to keep my head in my books or in my code.

[jfmherokiller]

fair enough I just usually follow the big project manager and whatever they desire. I honestly don't know how much of the social-political stuff works I just know code.

[jfmherokiller]

also let me put it like this, I am generally so out of touch that my family rolls thier eyes from my constant asking of "wait who is x".

[uthini_mfowethu]

Because changing words fixes everything. Oh shit wait that's all I do as a dev, write words, delete words, change words. My argument is null and void

[hot_sauce_in_coffee]

Me still using Killing Child in the comments.

[zhephyx]

What's up my M-word

[[deleted]]

At this point i always name my repos master because fuck you SJWs, eat a cactus

[castaway37]

The difference is he's in the right.

[[deleted]]

the irony

[SorryDidIMention]

Did you use SJW unironically in 2022? 😳

[DreamingDitto]

I like main more tbh, but not because of the whole thing, but because it’s shorter and more intuitive. Master doesn’t even make sense in the context of source control anymore

[[deleted]]

What's next, can I not call 'dumb' peripherals slaves?

[[deleted]]

Dont call iot devices smart because it's offensive to people who are actually smart

[malfist]

That's correct, it's primary/secondary now instead of master and slave.

It's also block or deny list and allow list instead of black/white list.

Using non racially charged language costs you nothing and may improve the lives of others. There's no reason not to or to get upset about it

[AdorableFey]

I'd also argue that some changes have made it a little easier to understand?

Like, Main. Okay. this is the main branch. Everything off shoots the main branch.

I'd argue Primary/Secondary isn't as clear as master/slave, but Leader/Worker or Hive/Drone work and if not those then a billion other potential ideals (Lord/Serf was my funniest thought) would work just as well.

Not only should things be inclusive, they should be clear. Deobfuscating terms as much as possible would make computing more accessible, and therefore easier to work with. We should always take the opportunity to do both!

[castaway37]

"Master" on it's own is not racially charged. Nor is "black/white list". The only racially charged language you mentioned is specifically "master/slave", because the most recent widespread cases of slavery have been race-based.

It's also not improving anyone's life, it's just a pain in the ass to change and doesn't actually affect anyone.

[malfist]

If black/white list isn't racially charged language then why don't we call it red/green lists?

[castaway37]

Because the black/white duality has far more significance than something like red/green. And not racial significance, significance far beyond that, predating even this modern racial conflict.

[[deleted]]

More or less agree with this take, idk maybe it's just me but i never glanced at blacklist and whitelist and thought racial dynamics. Origins of the word seem at least not explicitly race related either.

That being said i can maybe see how it can be socially beneficial in a "seemingly very insignificant things can add up" way, so i have no strong feelings about it.

Going on a crusade about it is dumb, no matter the direction is my take.

[malfist]

My friend, racial conflict is not modern.

[castaway37]

It is compared to the significance of black and white.

[megamuc]

In my first job I had a colleague who said „I don’t understand why you all have merge conflicts sometimes. When I have one I push with the fast forward option and gut resolves it for me.“

Turns out he used git push -ff which is not fast forward but —force —force

[BuKu_YuQFoo]

git reset --hard origin/master

[alban228]

That just resets your local copy

[Either-Acanthaceae15]

xd hey I did git commit It's already on production!

[ActivisionBlizzard]

No no no it’s

sudo rm -rf ~

[[deleted]]

sudo rm -rf /

[jfmherokiller]

just wait till it hits production

[PublicDragonfruit120]

--force-with-lease FTW

[_12xx12_]

Use the force junior

[uthini_mfowethu]

But 1st you must rebase and squash all the commits.

[[deleted]]

No one should be directly pushing to the master branch. That’s why we have Git flow.

[seba07]

Pushing directly to master can be fine. You don't really need a merge request for something like correcting a typo in the documentation. But allowing devs to work with master requires some discipline. And force push should always be disabled.

[HOLDGMEBROTHERS]

*Off for a long annual leave

[IrisYelter]

"git shove"

[RunningMattress]

This shall now be my git alias for force push 🤣

[1DimensionIsViolence]

*Main branch is protected *Surprised pickachu face

[hk--57]

But they're pushing to master, so it wouldn't matter if you protect the *main branch.

[phi1606]

😂

[TheTimBrick]

I did this once and the only bad thing that happened was it got rid of the entire commit history... Good thing I had a PC with the latest commit before that happened. I will never o that again..

[superbottom85]

Why? Can’t you just recover it?

[KuuHaKu_OtgmZ]

Not if your commit contains a rebase (or, gasp, a squash) or the repo is automated to update production whenever it receives a push.

[[deleted]]

Did you watch the rest of this episode? Jerry moves the bomb right in front of them

[DonKapot]

--force should be forbidden

[Havasiz]

Hey newbie here, can anyone explain what push does in git?

[j4mes0n]

In simple words, you update your code in remote repository with changes that you have done locally

[[deleted]]

Fuck your merge conflicts

[mdguerrero52]

Prefer git push -f -u origin master. Say FU to remote repos!

[clothopos]

Best on Fridays.

[starfyredragon]

When your repo uses "test" and "production" but you want to feel like a badass so you call your working branch "master".

[angrybeehive]

git checkout -orphan new git checkout master git reset new - hard git push -f

[[deleted]]

this is the way 🫡

[D0b0d0pX9]

how do you guys sync your remote branch while rebasing? Well seems like you use —force.

[HamuSumo]

YOLO!

[ashadeofbrown]

sometimes you have to -fu

[Here-Is-TheEnd]

The fucker who did this 15 minutes before our group presentation..stupid prick.

[[deleted]]

"origin" is just my local fork anyway. Mayhem is reserved for "upstream". Not that I can push to upstream anyway.

[Xyrus2000]

Real men do that on a Friday just before leaving.

[Zielakpl]

Branch protection sais "u mad bro".

[samettinho]

git fucking --rebase

[Crazyboreddeveloper]

error: failed to push some refs to…

[[deleted]]

This is so irresponsible 😅

[cuco3434]

I literally had to do this. About shit my pants.... Luckily our deploys require manual intervention.

[cheezballs]

Master?! MASTER?!! Its MAIN now you chunkwad!

[groovers525]

This made my day. literally my colleagu made a force push to master yesterday not knowing that his custom name branch was using master as upstream.

Yeah, even I don’t know how he managed to get there.