224 Advanced git [2d]

Goals

• Understand the differences between git diff and git diff --staged (or git diff --cached)
• Understand the difference between git reset and git reset --hard
• Use git add -p
• Use git checkout -p
  • Note you can also rollback partial changes from the line gutter in RubyMine.
• Use git rebase -i
  • Understand what it means for pushing to a remote, and for working with your colleagues
• Use git rebase --onto.
• What does git commit --amend do?
  • Understand what it means for pushing to a remote, and for working with your colleagues
• Understand the differences between git pull and git pull --rebase
  • You can opt to always use the latter if you want
• Use git revert <commit>
  • What happens? Is the reverted code lost?
• Use git cherry-pick <commit>
  • Understand our cherry-picking workflow for production and why it is necessary
• Use git reflog
  • When is this useful?
• Find out how to check out a file from another branch
  • Tip: Have a look at git checkout -- and git restore
• Remember our recommended git workflow for feature branches

Resources

• Atlassian Advanced Git Tutorial Show archive.org snapshot
• git built-in help (git help reflog etc.)
• Workflow for Splitting git Commits
• Howto: Write a proper git commit message
• Explanations for confusing git terminology Show archive.org snapshot

Exercises

While you are working on the movie DB as a single developer, real life applications are usually developed by entire teams. That means that local branches will frequently need to be rebased as they diverge from remote code. These exercises emulate such situations.

You are free to apply better naming conventions to the requested commit messages, they are only kept short here to fit inside the visualization.

Exercise 1: Split up the most recent commit

Head over to https://code.makandra.de/makandra/advanced-git-example-project and fork Show archive.org snapshot the repository to your private space. Ask your mentor to give you access to the repository.

Have a look at these branches and their commits:

Check out feature-documentation of your fork and rewrite its history into multiple commits using git rebase:

The hash of the commit new-git-repo should not change (785951a). Verify this by looking at git log --oneline.

Exercise 2: Split up an earlier commit

Now imagine you are the author of the branch feature-binaries.

You are now asked to split up the add binaries commit to one commit per binary.

Exercise 3: Rebase onto a diverged feature branch with merge conflicts

feature-echo was branched of feature-node while it only contained commit "add NPM". It added a new feature on it (add-echo-script).

In the meantime, feature-node was code reviewed, squashed and force pushed. It now looks like this:

Rebase feature-echo onto feature-node so it has this history:

The hash of the commit "setup node" should be identical within the two branches. Solve the resulting merge conflicts at the README so that the paragraph about the echo script comes after the introduction to Node.