Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
This is obviously wrong! #3
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:
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.