tools/
Git, the terminal, editors, debuggers and package managers.
4 results
tools/git-branches-why-making-one-doesn-t-copy-your-project.md
Git branches: why making one doesn't copy your project
When someone says "make a branch for that," it sounds like Git must copy your whole project. It doesn't. A branch is just a name stuck on…
tools/git-staging-area-why-saving-your-work-takes-git-add-and-git-commit.md
Git staging area: why saving your work takes git add and git commit
Why does saving your work in Git take two commands, `git add` and `git commit`? Because a change travels through three places: your working…
tools/git-merge-vs-rebase-same-code-two-different-histories.md
Git merge vs rebase: same code, two different histories
Git can combine two lines of work in two ways. Merge ties them together with a new commit and leaves every old commit alone. Rebase replays…
tools/git-basics-where-your-work-lives-and-why-branches-are-just-pointers.md
Git Basics: Where Your Work Lives and Why Branches Are Just Pointers
Git saves your project's history as commits: snapshots you choose to take, each with a short message. The trick to understanding it is…