930
In case of fire (lemmy.world)
top 50 comments
sorted by: hot top controversial new old
[-] arymandias@feddit.de 99 points 11 months ago

Me burning to death fixing pylint warnings before I can commit my code.

[-] Theharpyeagle@lemmy.world 17 points 11 months ago

Melting because someone didn't configure the right profile and now isort and black are fighting over imports.

[-] Oszilloraptor@feddit.de 76 points 11 months ago* (last edited 11 months ago)

Why is the wrong version always the one that is posted.

The (in my eyes) correct (and iirc original) version is:

  • Git commit
  • Git push
  • Get out*

*as someone pointed out (and I remember it as well, but thought I rembered it wrong and corrected it, shame on me in this context) the last point may be originally "git out"

[-] ChaosInstructor@lemmy.world 29 points 11 months ago

i might remember it wrong...but was it not 'git out'?

[-] Kidplayer_666@lemm.ee 5 points 11 months ago
load more comments (1 replies)
[-] uis@lemmy.world 12 points 11 months ago

Here git out is mentioned

[-] zero_gravitas@aussie.zone 7 points 11 months ago

That is so much better πŸ‘

load more comments (1 replies)
[-] Shizu@lemmy.world 56 points 11 months ago
[-] pivot_root@lemmy.world 21 points 11 months ago

Here at Company Inc, we continue to send our thoughts and prayers to the 38 interns who perished in the office fire of '07. Sixteen years later, we still mourn the loss caused by this unpredictable, unpreventable, and unlitigatable accident. We hope that, in time, the grieving families of those interns are eventually able to move on with both their hearts and their loved ones' funeral expense debts.

[-] pastermil@sh.itjust.works 10 points 11 months ago

Should've pulled first before starting your work.

[-] atyaz@reddthat.com 7 points 11 months ago

Sometimes my work takes a while and other people push in the meantime. Guess I'm dying the fire.

load more comments (3 replies)
[-] evilgiraffe666@ttrpg.network 6 points 11 months ago

On a push? What are you merging there?

[-] fushuan@lemm.ee 4 points 11 months ago

Ofc, you might be working directly on develop/master/shared branch, I know people that work in those environments (ew)

[-] evilgiraffe666@ttrpg.network 8 points 11 months ago

Right, on shared branch you might need to pull first if you're out of date (and you would be if you're all leaving the office at the same time), and that could cause a merge conflict.

It's like I always said, bad branching strategies are a fire safety issue.

[-] PrettyFlyForAFatGuy@lemmy.ml 48 points 11 months ago* (last edited 11 months ago)

i read a reddit post years ago where a someone wrote a script that iterates through all the projects in their dev folder, for each project creating a new branch, committing and pushing.

they then aliased it to "fire" or "panic" or something like that.

not a bad idea really

[-] flashgnash@lemm.ee 10 points 11 months ago

As in one they'd manually run if there was a fire?

[-] icedterminal@lemmy.world 7 points 11 months ago

Exactly. The alias just points to the script which is executed.

[-] flashgnash@lemm.ee 8 points 11 months ago

Ohh I see so you just run git fire?

[-] PrettyFlyForAFatGuy@lemmy.ml 6 points 11 months ago

if its aliased you should be able to just run "fire" and it does the rest

[-] flashgnash@lemm.ee 5 points 11 months ago

Oh bash alias right

[-] fushuan@lemm.ee 37 points 11 months ago

Slight correction. In case of fire:

Git checkout -b firemyusername Git commit -am="fire" Git push.

We don't want to have conflicts with code versions when going in on a rush, better to create a new branch. We can merge all the conflicts afterwards.

load more comments (10 replies)
[-] kd45@lemm.ee 35 points 11 months ago

Cause of death: 15 minute long pre-push hook

[-] redeven@lemmy.world 17 points 11 months ago

Just

git add . && git commit -m "sorry theres a fire" && git push -u origin feature/fire

And run out. It will eventually finish pushing. Or not.

load more comments (1 replies)
[-] Aurenkin@sh.itjust.works 29 points 11 months ago

In case of

Git commit

Git push origin main --force

Fire

[-] MoonRaven@feddit.nl 26 points 11 months ago
[-] dirtbiker509@lemm.ee 3 points 11 months ago

*git -tf out

[-] CaptainBlagbird@lemmy.world 25 points 11 months ago* (last edited 11 months ago)
load more comments (1 replies)
[-] lukas@lemmy.haigner.me 22 points 11 months ago
[-] osmn@lemmy.ml 18 points 11 months ago

"I followed the rules, Boss. Not my fault the rules are stupid πŸ€·β€β™‚οΈ"

load more comments (1 replies)
[-] HiddenLayer5@lemmy.ml 13 points 11 months ago* (last edited 11 months ago)

Counterpoint: Virtualized environment/remote desktop. The real computer is in a data center hundreds of kilometers away with world class fire suppression systems.

Counter counterpoint: If you're virtualized you might be working from home, in which case, that's rough, hope they manage to restore your house.

[-] RollForInitiative@feddit.de 4 points 11 months ago

With a laggy desktop experience i also can't really configure how i want? No thank you. It's bad enough i have to use Windows for software development instead of letting me install Linux

[-] HiddenLayer5@lemmy.ml 4 points 11 months ago* (last edited 11 months ago)

I like it because I don't have any of the company's shit on my own machine. I absolutely don't trust them not to spy on my personal computer use if they had access to it. With remote desktop I close it at the end of the work say and it has no more access to my computer than I have access to their critical systems.

In my case, their shit that we're required to use don't even support Linux so if it wasn't for virtualized environment I'd had to install Windows on my own machine.

load more comments (1 replies)
[-] Piemanding@sh.itjust.works 13 points 11 months ago

Mark this shit NSFW. I could have viewed it at work.

[-] xantoxis@lemmy.world 9 points 11 months ago

And if your git repo is self-hosted on-prem, you'd better be helping pack it and carry it out.

[-] nao@sh.itjust.works 9 points 11 months ago

no changes added to commit (use "git add" and/or "git commit -a")

[-] rufus@discuss.tchncs.de 3 points 11 months ago* (last edited 11 months ago)

It should (at least) be:

git commit -a -m "🚨πŸ”₯🚨"
git push --force

Better, create a new branch and push it to origin(?).

Relevant The IT Crowd

[-] IAm_A_Complete_Idiot@sh.itjust.works 4 points 11 months ago* (last edited 11 months ago)

Better have not created any new files tho - git commit -a doesn't catch those without an add first.

load more comments (2 replies)
[-] barsoap@lemm.ee 6 points 11 months ago

This is a lawsuit waiting to happen. Anyway any of you ever heard of ACID? Why aren't our undo buffers durable and integrated with version control? Squash and forget the individual keystrokes as soon as an actual commit is made.

[-] dirtySourdough@lemmy.world 6 points 11 months ago* (last edited 11 months ago)

I've got something similar on my office door that reads

In case of fire git commit -a git push git -tf out

[-] mercano@lemmy.world 6 points 11 months ago

First, git checkout -b omgFire, then do the rest.

[-] hakunawazo@lemmy.world 3 points 11 months ago

If the flames are nearby I would be so reckless and execute git push --force.
I don't want to die for a merge conflict.
But maybe then the team will burn me later.

[-] spongeborgcubepants@lemmy.world 2 points 11 months ago

Just push to a new branch

[-] netchami@sh.itjust.works 3 points 11 months ago

Commit message: It's litπŸ”₯πŸ”₯πŸ”₯

[-] soggy_kitty@sopuli.xyz 3 points 11 months ago

Sorry to be that guy but I don't think it's smart to put this anywhere in public, keep this shit somewhere private as a joke

load more comments
view more: next β€Ί
this post was submitted on 25 Nov 2023
930 points (97.3% liked)

Programmer Humor

32355 readers
1057 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS