New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

This is obviously wrong! #3

Closed
b005t3r opened this Issue Jul 26, 2017 · 1 comment

Comments

Projects
None yet
2 participants
@b005t3r

b005t3r commented Jul 26, 2017

I don't mind you messing with people's safety, but I do mind you messing with uncommited changes! These "in case of fire" instructions are obviously incorrect and will often result in engineers not being able to push their changes to the remote repo due to possible conflicts! This might cause project delays, missed deadlines and create unnecessary vacancies (some employees will surely die in flames, trying to find the solution on Stack Overflow, which will in turn create unplanned tasks for your HR department, etc. - it's just going to be a mess).

What your "in case of fire" board should say instead is this:

git checkout -b fire_[EMPLOYEE_UID]
git add -A .
git commit -m 'Fire!'
git push --set-upstream origin fire_[EMPLOYEE_UID]

Create a new branch, commit your changes there and push the branch to the remote! Easy, no conflicts, no uncommited changes, just a tiny bit of merging once the smoke clears! Woo-hoo!

PS. Some employees might still die in flames trying to find their ID - nothing can be done about that I'm afraid, so better get your HR department ready, just in case.

@louim

This comment has been minimized.

Show comment
Hide comment
@louim

louim Jul 26, 2017

Owner

Indeed! This was merely created to match the original meme. You might be interested in git-fire then, which does something pretty close to what you're describing! 🏃 🔥

Owner

louim commented Jul 26, 2017

Indeed! This was merely created to match the original meme. You might be interested in git-fire then, which does something pretty close to what you're describing! 🏃 🔥

@louim louim closed this Jul 26, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment