You must log in or register to comment.
First, git checkout -b omgFire, then do the rest.
I’ve got something similar on my office door that reads
In case of fire<br> git commit -a<br> git push<br> git -tf out
Commit message: It’s lit🔥🔥🔥
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.
Oh man I hadn’t seen a
git checkout -bin years haha since they introducedswitchandrestore, never looked backI’ll admit I just press the buttons in my favourite IDE and had to look up the commands to remind myself, but yeah.
Isn’t that what git stash is for though?
Can’t push a stash
git push origin refs/stash@{$n}:stash/$USER/$niircCan’t you? Could’ve sworn you could
I’ve done it with TFS source control at least, thought it would be possible with git
Gonna need some semicolons or double ampersand in there
Nah, what I need is doble new lines of code blocks since this is markdown and it fucked the display.
Here you go:
git checkout -b firemyusername git commit -am="fire" git pushI know how to do it, I was just lazy lmao.
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
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.
Mark this shit NSFW. I could have viewed it at work.
Me burning to death fixing pylint warnings before I can commit my code.
Melting because someone didn’t configure the right profile and now isort and black are fighting over imports.
In case of
Git commit
Git push origin main --force
Fire
Merge conflict
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.
Should’ve pulled first before starting your work.
Sometimes my work takes a while and other people push in the meantime. Guess I’m dying the fire.
Then you pull before committing.
Boom, merge conflict. The only thing left to me is force push and delete everyone’s changes.
Eh, it’s probably fine. Those chumps don’t do anything useful.
On a push? What are you merging there?
Ofc, you might be working directly on develop/master/shared branch, I know people that work in those environments (ew)
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.
Cause of death: 15 minute long pre-push hook
Just
git add . && git commit -m "sorry theres a fire" && git push -u origin feature/fireAnd run out. It will eventually finish pushing. Or not.
git add .; git commit -nm fire --no-gpgsign; git push -n origin fire/${USER}
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.Just push to a new branch
*git out
*git -tf out
deleted by creator
What about
git add?You could change it to
git commit .to add and commit everything. But just in case you weren’t up to date, you should probably dogit commit . git pull -s ours git pushFor maximum chaos.
“I followed the rules, Boss. Not my fault the rules are stupid 🤷♂️”
