Git is hard: screwing up is easy, and figuring out how to fix your mistakes is fucking impossible. Git documentation has this chicken and egg problem where you can't search for how to get yourself out of a mess, unless you already know the name of the thing you need to know about in order to fix your problem.
So here are some bad situations I've gotten myself into, and how I eventually got myself out of them in plain english.
Interactive rebase is one of Git’s most versatile tools. Here's how to use it to correct commit messages, fix mistakes, and more.
Ständig versuchen Leute Git richtig zu erklären. So auch ich, schließlich hat sich Git schon seit einigen Jahren als Standard festgesetzt...
Sync a fork of a repository to keep it up-to-date with the upstream repository.
simple terminal UI for git commands. Contribute to jesseduffield/lazygit development by creating an account on GitHub.
