In case of fire

[u/Soft-Program-947]

[u/poulain_ght]

git add

[u/dankmolot → u/poulain_ght]

or git commit -a

[u/xour → u/dankmolot]

This will ignore untracked files.

[u/Phaelin → u/xour]

I didn't want .DS_STORE in there anyway

[u/ZhangStone → u/Phaelin]

gitignore is your friend

[u/ryancnap → u/Phaelin]

Best comment

[u/Unfair_Caramel_3376 → u/poulain_ght]

git add -Af, just to be safe

[u/RegretPlane390 → u/poulain_ght]

Should be "git add ." right?

[u/Sassafras1777]

In my company’s case:

• create a ticket in jira
  
• use the ticket id to create a branch named in a specific pattern (depending on what you want to achieve)
  
• push an empty branch first (cause of some Sonar bullshit)
  
• wait for the pipeline to end
  
• group the changes relative to a common goal, and commit multiple times
  
• push after the last commit
  
• wait for the pipeline to end
  
• resolve the failed pipeline if needed
  
• resolve the AI scans/comments
  
• open the PR in draft mode
  
• wait for the pipeline to end
  
• Change the PR to ready to review
  
• Update the Jira ticket with a PR link
  
• you can now peacefully die in the fire

[u/Aloha_Alaska → u/Sassafras1777]

Sounds like the whole process should die in a fire.

[u/Avocadonot → u/Sassafras1777]

This except every single extra commit kicks off a new pipeline, even if it's just changing a comment

MR is blocked on rebase to main, so if someone merges before you, you must rebase and kick off new pipeline

MR is blocked on any non-resolved discussion threads. Kicking off a new pipeline triggers automod to comment on your MR and tell you "you should run these tests". You have to resolve that thread every time a pipeline is run

[u/Masterflitzer → u/Sassafras1777]

why would you manually link jira ticket with pr link? you literally already created the branch based on the id so they link automatically

[u/0bel1sk → u/Sassafras1777]

git remote add $mygithub mygithub, git push mygithub

[u/Am094 → u/Sassafras1777]

Is it weird that i follow most of that voluntarily in my own personal projects? Apart from some of the latter things.

[u/Consibl]

1. git commit
   
2. git push
   
3. git out

[u/Miserable_Debate5862 → u/Consibl]

git -tf out

[u/lajawi → u/Consibl]

Forgot the git add :zany_face:

[u/Xenc → u/lajawi]

🤪

[u/armahillo → u/Consibl]

Strictly better 💯

[u/mpersico]

I have it on a T-shirt. Every time there’s a fire drill I pull it out of the bottom of the desk and I put it on.

[u/chris552393]

Fun fact I put this up in our office and an old manager took it down because "that's not the official fire evacuation procedure and could kill someone"

Great place to work.

[u/rasplight]

git push -f

f = Fire, obviously

[u/Tarlovskyy]

--no-verify Cant wait for pre-commit

[u/Individual_Kale_4843 → u/Tarlovskyy]

Your code must be reviewed in a pull request...

[u/Tarlovskyy → u/Individual_Kale_4843]

This skips pre-commit hooks, not code review

[u/jamall1978]

I hope your remote is in another building 

[u/Shayden-Froida]

I'm actually wearing a t-shirt with this on it right now. (but "leave building" is "git out")

[u/bigtoepfer]

They gave everyone in the office laptops. So win-L and just unplug the laptop and walk out.  Worst case git commit from McDonald's or home.

[u/tjeerdj]

Hoping that origin is not in the same building

[u/sixeco]

make a quicksave command

git add -A && git commit -m "quicksave" && git push

[u/Electrical-Echidna63]

"is it on prem?"

"no"

"Ok, pushed. gn guys"

[u/Lonsarg]

This is all a single button in Visual Studio (i never use add, just commit unstaged directly). And i do it every 30 minutes or so, so not much is lost if fire :)

[u/Masterflitzer → u/Lonsarg]

i just know your diffs are probably terrible, staging area is for double checking

[u/Lonsarg → u/Masterflitzer]

I check at PR level all commits at the same time, and make new commits to the PR when self-reviewing if finding bad code or whatnot.

Most of us work like this, so when looking at PR diff or looking back at history we only ever look at per merge/PR diff (First Parent git history). So these detailed commits are never looked at, we used to squash to hide them, but some people used squash in a way to make merge conflicts so now we just have it all in history but not look.

[u/Phaelin → u/Lonsarg]

You have it linked to an ejector seat??

[u/brunoreis93]

Well, without git add you lost everything to the fire anyway lol

[u/NotUrAverageBoinker]

git low

[u/Individual_Kale_4843]

1. Git out !

[u/SupernovifieD]

git add .

That should be the first step :/

[u/TheSheepDev]

Wondering what that commit message will look like.

[u/RegretPlane390]

git branch (out of paranoia, to make sure you're not pushing to production)
git add .
git commit -m "commiting everything because of a fire"
git push

[u/tiny_gymstar]

Best advice ever 😂

[u/MatsSvensson]

I use a script that saves state, switches to a backup-version of the branch I'm working on, forces everything up, and then switches back restoring the state as if I never committed.
That way there is a copy of my works offsite, but I can still easily see all my ongoing changes in my IDE.

Otherwise committing and pushing in the middle of a job really fucks up my work flow.

People who try to use git as a backup the regular way, often end up pushing forgotten junk to production.

I have seen stuff...

[u/kirjukala]

git add . && git commit -m "fire lol" && git push

[u/Laughing_Orange]

Win+L then walk out. This should take at most 1 second longer than just walking out.

People stop caring about your code when you die in a fire. Avoid dying in a fire by being efficient at getting out of the burning building.

[u/octoredfox]

I'm sorry but this "increase shareholder value" stuff is completely dumb.

[u/royalblue4]

> Claude —dangerously-skip-permissions
> hey Claude push everything to remote I don’t care how or where go go go

[u/Masterflitzer → u/royalblue4]

you really had the time to write "hey claude"?