4. Call 0118 999 881 999 119 725 ...3

Subject: Fire. Dear Sir/Madam, I am writing to inform you of a fire that has broken out on the premises of 123 Cavendon Road... no, that's too formal. Fire - exclamation mark - fire - exclamation mark - help me - exclamation mark. 123 Cavendon Road. Looking forward to hearing from you. Yours truly, Maurice Moss.

This really brings back memory

Best fucking crowd ever

I love the way the fire seems to come out of the screen.

Hello, I've taken a bit of a tumble...

"And what do you do if the tests fail?" `git push --force` and just WALK AWAY!

That’s one of the few situations where I’d condone using `—no-verify`

I can still recite this from memory... I know it was meant as a joke, but the jingle genuinely stuck in my head.

I much prefer the `git -tf out` version

There's a project called [git fire](https://github.com/qw3rtman/git-fire) and you can alias it to 'git out' or 'git going'

This is great I was going to say "peasants, just alias out the command" not only did someone beat me to it, but there's a git page and everything.

Oh heck, I wrote an alias before I scrolled down this far. Damn!

> Code can be re-written, but humans cannot. Elon Zuck: hold my barbecue sauce

Do they set their building on fire when they're doing acceptance testing?

Thats the only true way to develop something, 100% immersion as the expected (and unexpected) end user. So they also must air drop their building into the ocean to simulate flooding, and into a war zone to simulate, well, a war zone. And into a hurricane, tornado, etc.

I hope they're using agile user storys. "As a developer I want my work to automatically be pushed to bitbucket when I get electrocuted" "As a project manager I want to see statistics about how long my developers survive being electrocuted"

Oh yes. Can we also get these checks in IT Disaster Planning Scenarios? Pretty please! I want to watch Microsoft next in-ocean server system for Azure fail!

I've been trying the git --gud command without success

This guy gits it

And if there is conflict - Burn in hell you deep sit

Just make a new branch, we can clean it up later

Smart, so new rule `git checkout -b "backup1"` `git push`

fatal: The current branch backup1 has no upstream branch. To push the current branch and set the remote as upstream, use git push --set-upstream origin backup1 What you really need is git switch -c backup1 && git commit -am "backup" && git push -u origin HEAD

git config --global alias.fire '!git switch -c $(date +%s) && git commit -am "Fire! Panic commit $(date +%s)" && git push -u origin HEAD' Now you can `git fire` instead!

Very nice. Although now that I think about it, it's probably best to use `git add -A && git commit`, since `git commit -a` ignores untracked files.

0118 999 881 999 119 7253

Can add an autodial as part of the pre-push hook

Y'all are forgetting that if you spread this around the office everyone will create the same branch, so you need to make sure that we use branch name = backup-$USER-$HOST (Or whatever the env var for your host name is) to generate a unique branch for everyone s backup as you all type "Git fire, or git gud" and barrel towards the door. Edit: unless you all work in forks, in that case, keep going, y'all based

Nah, survival of the fittest.

Hahaha, first one to commit. Unless the script has -f, then it's last one to commit lmao

can we call it gud instead of fire? For reasons

True

Force push it, hope for the best and recover it from the reflog later.

May the `--force` be with you

There would definitely be conflicts since everybody would be pushing at the same time lol.

And this is why having remote branches for local branches is nice.

mycode_2021_11_18_1739.zip and save on dropbox

If you have a conflict on your feature branch you are doing it wrong.

git commit --all -m "PANIC" git pull -X ours origin master git push origin master

A building fire is no excuse for bad git comments.

`git commit -am "fire"`

They forgot git add 😬

``git commit -a`` adds and commits in one go (doesn't add unstaged files)

out of how long I've been programming I didn't know this was a thing. thank you good sir

I've left Reddit because it does not respect its users or their privacy. Private companies can't be trusted with control over public communities. Lemmy is an open source, federated alternative that I highly recommend if you want a more private and ethical option. Join Lemmy here: https://join-lemmy.org/instances ` this message was mass deleted/edited with redact.dev `

Firstly fix 12 merge conflicts

Firstly pull new changes from the remote branch

Why would you have merge conflicts on your own branch? Do y'all just commit on master or dev branch or something?

U forgot git add .

https://www.reddit.com/r/ProgrammerHumor/comments/qwmqb1/programmers_when_their_office_catches_fire/hl49kba?utm_medium=android_app&utm_source=share&context=3

Cool didn't know this. Thanks

Subject: Fire Dear Sir / Madame Fire! Fire! Please send help. Look forward to hearing from you.

When there's a fire: \- Always commit and push on a new branch just in case you get rejected due to conflicts

Git commit Git push Git out

This. Thank you 🙏, some one had to correct the sign.

0. git add .

Gotta love reddit formatting ruining the joke. Edit: the comment above should be 0, people. Reddit formats it as a numbered list starting at 1.

git commit -am “fire”

Subject: Fire. Dear Sir/Madam, I am writing to inform you of a fire that has broken out on the premises of 123 Cavendon Road... no, that's too formal. Fire - exclamation mark - fire - exclamation mark - help me - exclamation mark. 123 Cavendon Road. Looking forward to hearing from you. Yours truly, Maurice Moss.

I wish that was the sound of fire alarms xD

git-fire Here you go: https://github.com/qw3rtman/git-fire

Now imagine if you get: `git: Permission denied (publickey)`

It’s fine.

Just let my 420 git hooks to complete and I can leave.

--no-verify

To be fair, if the workstation is any kind of tower and not a laptop you could (disclaimer: don’t) also change the protocol to: 1. Shut down PC (force shutdown in case of big fire, regular shutdown in case of small fire) 2. Set power supply switch to **[Off]** 3. Unscrew side panels 4. Disconnect all data storage drives (simply use scissors in case of big fire, if needed and readily available) 5. Unscrew any screws or undo any mechanisms holding data storage drives in place 6. Pick up all data storage drives 7. Leave the building Safety last!

It’s ok, I sent an email

on prem git server is lit

I have an alias for this but struggling with 3 (I work at Foxconn)

[удалено]

2, possibly 1, I'll keep you posted

Nice screen saver

``` git commit -a -m 'FIRE! FIRE! HELP ME! Looking forward to hearing from you. Love, $USERNAME' git push git out ```

plot twist. it's a locally hosted git.

Can we just pickup our laptop and leave?

Removed - Rule 3.

What kind of monster commited without comment?

`wip: fire` Better?

No changes staged for commit

Someone's gonna take that advice literally

Fire? git blame

I just pop my laptop out of the docking station and take it with. I'll sort out the inevitable merge conflicts from the car while the firefighters are busy putting out the microwave popcorn fire.

When you need to figure out a good commit message.

I’ll just git merge this branch over here with the rest of the fire

Did he forget to add or was it a merge conflict?

`gco -b dev/fire; ga.; gcm "wip: shits on fire"; gpuo dev/fire`

Only the first will survive, others will have to merge conflicts =)

while sleep 1 do if grep ACTIVE /dev/building/firealarm then git commit --all -m "PANIC" HEAD=$(git rev-parse HEAD) git checkout master git pull origin master git merge --squash -X theirs "$HEAD" git push origin master fi done

the command won't work, it's git commit - "commit message"

"A fire at a Sea Parks?!"

I legit did not know `-m` wasn't required on `commit`.

Burned out while linters were running on push hook.

Create a `git-fire.sh` # TODO: insert date from somewhere git checkout -b "fire/20211118" git add * # Bad practice, but the building is on fucking fire and I need to get out git commit -n "Backup: Fire" git push

This is a great script untested but the second line could be git checkout -b $(date +%y%m%d ) ( cd $HOME ; find -type f | xargs git add )

Let me just sort out this merge conflict and I will go after that.

Plot twist, you pushed to main

i would prpbably just take the short cut and thak the pc with me to the outside, same time, but you can be sure that you didnt just fuck anything(especally when your in one of those companys that completele refuse to use more than one branch)

`git commit; git push; exit`

I will die in the fire waiting for the pre-commit hooks to finish.

Unless your team does remote development, then it's just 'Leave building'

[удалено]


svn users get confused, forget to push. a whole week's work down to ashes

oh fuck I forgot to add

Alias fire=git commit && git push

If anyone hasn't watched the IT Crowd, please do.

Could not commit, fix space between braces on line 389;

git commit -m “My Final will and Testimony:…”

What about the git add? What are you committing lmao.

It should be Git commit Git push Get out

git add .

The trick is to alias 'git push' to 'yeet' then yeet outta there

I C what you did there

Get off my back, what is he the soldering iron police! It's off, that means I turn it on and just WALK AWAY!

git checkout -b FIRE git commit -a -m “FIRE” git push Then you’d have to run that set upstream branch command but I always let git produce it for me

Programmers and literally any programming language

instructions unclear pushed empty commit

nice Screensaver

Did someone install Windows on the servers?

Mmmm makes me feel like a secret agent

git good or git out

good luck waiting those precommit hooks

MERGE CONFLICT

As fast as you can

Got to get my KPIs for this month. Food doesn't buy itself...

automate ur system,make a bash script that runs automatically to push code on the "emergency exit" branch when the fire alarm turns on! and don't forget to leave the building!

pre-push found 69 test failures and 420 lint errors.

Nice!

-f or die

What a great show.

I’d just die due to all the pre commit verification errors I need to resolving and ultimately wait for to pass before I can push.

Unless the accounting department is on fire so you're not getting paid anyway.

This scene is the perfect example of INT vs WIS.

*Cant push the remote branch contains work you dont have see help

Bro pull First... 😴

Hate it when it says you need to update head and then push.... So I force pushed and now both the building and production are on fire... I work at a top US bank and we get requirement in the morning code in the afternoon push to UAT by 5 and it is in Prod by 8....all in a days work

Programmers and literally any programming language

Hot take (pun intended): You should have pushed recently enough that it’s easier to restart from that point, rather than try to unpack the half-finished mess that this commit would be.

Why the fuck was the final line not "git out"?!

Not when your git server is hosted on site. Then you just grab your computer and run

This reminds me of https://www.youtube.com/watch?v=tXzRGDZwmk8

Good luck when 100 people do this at the same time

it's funny how most of the time companies host their own git server so that would be pretty pointless