What it is
Git Flight Rules is a recovery and troubleshooting guide for common Git problems. The name refers to aviation flight rules: predefined actions for when something goes wrong during flight.
Git is powerful but stressful; one wrong command can scare even experienced developers if the current state is unclear. This catalog page treats the project as a concrete tool with context, typical use cases, and limits, not just as a ranked repository.
What is inside
The repository is a Markdown guide with sections for commits, branches, rebase, merge, stash, remotes, and recovery.
The material is organized as situations and solutions, making it useful during an actual problem. That repository shape helps readers understand whether they are looking at a library, an application, a learning course, or a reference guide.
How it is used
Developers use the guide to recover work, fix history, undo actions, or choose a safe command.
The best use is to read the whole scenario, inspect `git status` and `git log`, and only then run commands. A good first step is to repeat the small scenario below and then test the project against your own data, code, or team task.
Strengths and limits
The strength is calm practicality: it turns panic into checkable steps.
The limitation is that every Git state is specific; recipes must be matched to the current commit graph.
The practical value of Git Flight Rules is easiest to see through a small verifiable scenario: take the task the project was made for and follow it to a result. Git Flight Rules collects practical recipes for unpleasant Git situations: wrong commits, lost branches, conflicts, bad rebases, and accidental history changes. That makes the project easier to judge by actual work removed from the team.
If Git Flight Rules remains in use beyond the first experiment, maintenance, updates, access rules, license terms, and clear ownership become as important as features. That is where the difference between an interesting repository and a durable product dependency usually appears.
Git Flight Rules is also easier to understand through practice than through metadata alone. It has a concrete audience, a typical adoption path, and conditions where it becomes useful or unnecessary.
Example
Проверка перед исправлением Git-истории
Пример показывает безопасную привычку: сначала посмотреть состояние и граф, а уже потом выбирать рецепт.
git status
git log --oneline --decorate --graph -12