Hysen Labsgit-flight-rules
Flight rules for git
git-flight-rules: what to do when git fights back
When git goes wrong, where do you look? This guide, modeled on NASA flight rules, collects step by step answers organized around real situations like cloning a repository and setting the wrong remote.
Where the name comes from
The repository calls itself flight rules for git, and the README explains the analogy. Flight rules are hard earned knowledge recorded in manuals that list, step by step, what to do if something occurs and why. The guide is described as being for astronauts, now programmers using Git, about what to do when things go wrong. The project is licensed under CC-BY-SA-4.0.
The NASA connection
The README notes that NASA has been capturing missteps, disasters, and solutions since the early 1960s, when Mercury era ground teams gathered lessons learned into a compendium listing thousands of problematic situations and their solutions. It quotes the definition that flight rules are extremely detailed, scenario specific standard operating procedures. That origin story explains both the name and the format.
How the guide is organized
The content is organized by scenario, such as wanting to clone a remote repository and setting the wrong remote repository. Each scenario gives steps for what to do. The README explains that all examples use a customized bash prompt to indicate the current branch and staged changes, with the branch in parentheses and a marker next to staged changes. It states all commands should work for at least git version 2.13.0 and points to the git website for updating.
Who it is for
The README frames the guide as useful for any git user, since everyone eventually hits a git problem that needs a known solution. The scenario based format means you can jump straight to the situation you are in rather than reading linearly. For anyone who has ever typed the wrong git command and wanted a checklist, that is exactly the shape this takes.
Community notes