A repository to practice your git skills with. Exercises will be outlined in this Readme, where you can check out various branches and modify them in Git, to show off your skills ;)
This repository has a bunch of protected branches that are in various states. The exercises below use these branches and will ask you to modify them locally so they achieve what the exercise asks for.
This exercise will explore rewriting the commit message of your latest commit on your branch. A common use case for this is making your commit message more descriptive before pushing your code and saying it is ready to be reviewed. Or that a reviewer of your code thinks you should modify your commit message to make it more descriptive.
Exercise
Check out the branch exercise-latest-commit-rewrite.
Confirm that if you run git --no-pager log --pretty=format:%s 81795d5..HEAD you see the following:
git --no-pager log --pretty=format:%s 81795d5..HEAD
CHANGE ME
This command shows the commit messages between the HEAD of your branch and the commit where exercise-latest-commit-rewrite branched off of (if there is a % that can be ignored).
Change the message of the latest commit so that it instead displays the following:
git --no-pager log --pretty=format:%s 81795d5..HEAD
changed%
This exercise will explore adding more content to your existing commit. This is very handy if you have already made a commit but forgot to include something that you subsequently need to add. Or for example if you get comments and feedback during a review, that you want to add to your code without creating additional commits.
Exercise
Check out the branch exercise-latest-commit-add-file.
Confirm that if you run git --no-pager diff -r ffd218f HEAD you see the following:
git --no-pager diff -r ffd218f HEAD
diff --git a/some_file.txt b/some_file.txt
new file mode 100644
index 0000000..c915c72
--- /dev/null
+++ b/some_file.txt
@@ -0,0 +1 @@
+A file to demonstrate adding to commits.
This command shows the changes between the HEAD of your branch and the commit where exercise-latest-commit-add-file branched off of (The actual changes is what's important here, not the info at the top).
Add to the latest commit so that we include another line in the file:
git --no-pager diff -r ffd218f HEAD
diff --git a/some_file.txt b/some_file.txt
new file mode 100644
index 0000000..b835cea
--- /dev/null
+++ b/some_file.txt
@@ -0,0 +1,2 @@
+A file to demonstrate adding to commits.
+Changes I've added!
This exercise will explore rebasing. Rebasing is very nice as it allows us to have a clean commit history, and avoids messy merges. Doing a basic rebase is also the building block of doing more interesting techniques, such as the interactive rebase, which is where all the magic happens.
Exercise
In this exercise we'll be playing with two branches. The first one is exercise-rebasing-base. Pretend to see this one as the 'main' branch in your repo. This is typically the branch you want to merge your work into eventually. The other branch we will be using is exercise-rebasing-rebase-branch. Pretend this is your 'feature' branch that you've been doing development on.
The key thing to notice here is that work has been happening on our base branch after we branched off with our feature branch. If you do git log origin/exercise-rebasing-rebase-branch you can see that there is a commit to 'add sample file 2', however you can't see the 'add sample file 1' commit. This is because we branched off of the base branch before this commit happened (we branched off at b9dd7a0). If you do git log origin/exercise-rebasing-base you can see that we've added the 'add sample file 1' commit after where we branched off.
Check out the branch exercise-rebasing-rebase-branch and run git --no-pager log --pretty=format:%s b9dd7a0..HEAD to confirm you can only see the 'add sample file 2' commit:
git --no-pager log --pretty=format:%s b9dd7a0..HEAD
add sample file 2 (should be applied after sample file 1)
Rebase exercise-rebasing-rebase-branch onto exercise-rebasing-base so that the 'feature' branch will have its commits on top of the 'base' branch. Output should look like this:
git --no-pager log --pretty=format:%s b9dd7a0..HEAD
add sample file 2 (should be applied after sample file 1)
add sample file 1 (should be applied before sample file 2)
If you do a simple git log you should now see that the base of your feature branch is again on top of the base branch, with your extra commit adding file 2.
Sometimes when we rebase, there could be conflicts, which is what this exercise explores. They are no different to merge conflicts, except that they happen when you rebase.
Exercise
Base branch: exercise-rebase-conflict-base
Feature branch: exercise-rebase-conflict-feature
Similar to the other rebasing exercise above, in this one we want to rebase a 'feature' branch on top of a 'base' branch. However, this time there will be conflicts... The base branch has 2 commits: 1 that adds a file, and a subsequent 1 that appends a sentence in the file. The feature branch branched off of the base branch after the file was added but before the sentence was appended. The feature branch has 1 commit that prepends a sentence to the same file.
Check out the branch exercise-rebase-conflict-feature and run git --no-pager log --pretty=format:%s 7a8be75..HEAD to confirm you can only see the 'prepend sentence' commit:
git --no-pager log --pretty=format:%s 7a8be75..HEAD
prepend sentence to rebase example file
Rebase exercise-rebase-conflict-feature onto exercise-rebase-conflict-base so that the 'feature' branch will have its commits on top of the 'base' branch. As part of this you will need to resolve some conflicts. The commits should look like this:
git --no-pager log --pretty=format:%s 7a8be75..HEAD
prepend sentence to rebase example file
append sentence to rebase example file
rebase_example.txt should look like this:
This sentence is added on the feature branch and should be at the beginning. This is a text file to showcase rebasing with conflicts. This sentence is added on the base branch and should be at the end.
If you do a simple git log you should now see that the base of your feature branch is again on top of the base branch, with your extra commit adding file 2.
This is similar to our earlier exercise where we rewrote a commit. However, this time it is not our latest commit, so it is a bit trickier to do it. Again a typical use case here is if you want to make your commit messages more descriptive before pushing your code and saying it is ready to be reviewed.
Exercise
This time, we have the branch exercise-rewrite-early-commit with two commits on it:
git --no-pager log --pretty=format:%s 33dc87..HEAD
the world's most perfect commit message that no one should ruin
CHANGE ME
Note that the 'CHANGE ME' commit is after your perfect commit message. I.e. we don't want to ruin our already perfect commit message.
Change the 'CHANGE ME' commit message to instead say 'changed'. The other commit message should stay the same.
git --no-pager log --pretty=format:%s 33dc87..HEAD
the world's most perfect commit message that no one should ruin
changed
This is similar to our earlier exercise where we added to a commit. However, this time it is not our latest commit, so it is a bit trickier to do it. Again a typical use case here is if you want to add something to your commit based on feedback in a review. E.g. if you have two atomic commits being reviewed, and you get feedback on code that was in your earliest commit so you want to change that (e.g. you forgot to add tests).
Exercise
This time, we have the branch exercise-early-commit-add with two commits on it. We want to change the file file_to_modify.txt added in f4016d0 (1 commit before the tip of the branch):
git --no-pager diff 0f0606 exercise-early-commit-add~1
diff --git a/file_to_modify.txt b/file_to_modify.txt
new file mode 100644
index 0000000..86a11f6
--- /dev/null
+++ b/file_to_modify.txt
@@ -0,0 +1 @@
+Add a line below this one
Change the second to last commit so that you add an extra line to the file:
git --no-pager diff 0f0606 exercise-early-commit-add~1
diff --git a/file_to_modify.txt b/file_to_modify.txt
new file mode 100644
index 0000000..5ad6477
--- /dev/null
+++ b/file_to_modify.txt
@@ -0,0 +1,2 @@
+Add a line below this one
+Hi there, I'm a new line
The other commit should stay the same.
Often we might want to combine commits into each other and have them be one single commit. E.g. you might develop your code so that you have tests in one commit, and the implementation in the other. In the end though, you probably want to combine those two commits into a single commit that "implement feature X".
If we want to keep the commit messages we do what's called a 'squash'.
Exercise
This time, we have the branch exercise-combining-squash with two commits on it, one creating a file, the other one modifying it:
git --no-pager log 10b3c1..exercise-combining-squash
commit 7342c0fe1bd2720ee131e03ff43d4fb8174dca7b (HEAD -> exercise-combining-squash)
Author: Martin Husbyn <[email protected]>
Date: Wed Oct 26 16:26:40 2022 +0100
second commit to demonstrate squashing
commit 41df7384472aeda42eb4cd710572d19a42476cc5
Author: Martin Husbyn <[email protected]>
Date: Wed Oct 26 16:25:03 2022 +0100
first commit to demonstrate squashing
Merge the two commits into one, but keep their commit messages. Then you should end up with just one commit:
git --no-pager log 10b3c1..exercise-combining-squash
commit a1fd020b88b658869d8e388e93c9dbfb4b4af04e (HEAD -> exercise-combining-squash)
Author: Martin Husbyn <[email protected]>
Date: Wed Oct 26 16:25:03 2022 +0100
first commit to demonstrate squashing
second commit to demonstrate squashing
If we don't want to keep all commit messages, we do what's called a 'fixup'.
Exercise
This time, we have the branch exercise-combining-fixup with two commits on it, both creating a file:
git --no-pager log --stat 273091d..exercise-combining-fixup
commit 9ea9ed8948cbfd5aae117389c9b1ca3bdec09bbf (HEAD -> exercise-combining-fixup)
Author: Martin Husbyn <[email protected]>
Date: Wed Oct 26 16:42:48 2022 +0100
commit to throw away
fixup_file2.txt | 1 +
1 file changed, 1 insertion(+)
commit 5de8fee24babba8262e831d1a74fddfcd5a1c425
Author: Martin Husbyn <[email protected]>
Date: Wed Oct 26 16:37:44 2022 +0100
commit that should be kept
fixup_file.txt | 1 +
1 file changed, 1 insertion(+)
Merge the last commit into the first one, but only keep the first one's commit message. Then you should end up with just one commit:
git --no-pager log --stat 273091d..exercise-combining-fixup
commit 37de61bef0a41e124cd099d28677e45a15ce6333 (HEAD -> exercise-combining-fixup)
Author: Martin Husbyn <[email protected]>
Date: Wed Oct 26 16:37:44 2022 +0100
commit that should be kept
fixup_file.txt | 1 +
fixup_file2.txt | 1 +
2 files changed, 2 insertions(+)
Sometimes you want to also delete commits. This allows us to have a cleaner git history over having separate commits 'undoing' what previous commits have done.
Exercise
This time, we have the branch exercise-delete-commit with two commits on it, both creating a file:
git --no-pager log --stat 3a900ac..exercise-delete-commit
commit da199128bd3d7658f46d1ae95feb1e76ab419faa (HEAD -> exercise-delete-commit, origin/exercise-delete-commit)
Author: Martin Husbyn <[email protected]>
Date: Wed Oct 26 17:07:27 2022 +0100
this commit should be kept
keep_me.txt | 1 +
1 file changed, 1 insertion(+)
commit e2e39021ee492e0d3c46b22b0268bd45afc28b7c
Author: Martin Husbyn <[email protected]>
Date: Wed Oct 26 17:06:49 2022 +0100
this commit should be deleted
delete_me.txt | 1 +
1 file changed, 1 insertion(+)
Delete the first commit so we end up with only the second commit:
git --no-pager log --stat 3a900ac..exercise-delete-commit
commit 0ec0b80a1ef960d8b6599aa6df900930fe73cd2e (HEAD -> exercise-delete-commit)
Author: Martin Husbyn <[email protected]>
Date: Wed Oct 26 17:07:27 2022 +0100
this commit should be kept
keep_me.txt | 1 +
1 file changed, 1 insertion(+)
Sometimes we might want to change the ordering of commits. E.g. you might want to change the order so it follows a more logical development path, or group related commits together in the git log.
Exercise
This time, we have the branch exercise-reorder-commits with two commits on it, both creating a file, but they are in the wrong order:
git --no-pager log --stat a29ea2..exercise-reorder-commits
commit 2dcca9af417a3c90714fc436444c79e1bd798d58 (HEAD -> exercise-reorder-commits)
Author: Martin Husbyn <[email protected]>
Date: Wed Oct 26 17:18:54 2022 +0100
this commit should be first
first.txt | 1 +
1 file changed, 1 insertion(+)
commit adf290bb85ec6c10a6ead690c00f8b59f806e8d0
Author: Martin Husbyn <[email protected]>
Date: Wed Oct 26 17:18:30 2022 +0100
this commit should be last
last.txt | 1 +
1 file changed, 1 insertion(+)
Change the order of the commits so that they are in the right order:
git --no-pager log --stat a29ea2..exercise-reorder-commits
commit fbf35bfa14e63455ee7f4192da10bb292c5fc072 (HEAD -> exercise-reorder-commits)
Author: Martin Husbyn <[email protected]>
Date: Wed Oct 26 17:18:30 2022 +0100
this commit should be last
last.txt | 1 +
1 file changed, 1 insertion(+)
commit 9d76ea89ea1c15485edee886aca101e80da4ae97
Author: Martin Husbyn <[email protected]>
Date: Wed Oct 26 17:18:54 2022 +0100
this commit should be first
first.txt | 1 +
1 file changed, 1 insertion(+)
Sometimes we want to combine commits, but there are commits in between them so it's not a straight squash/fixup.
Exercise
This time, we have the branch exercise-combine-nonsequential with three commits on it, forming a 'sandwich':
git --no-pager log 7e651b879..exercise-combine-nonsequential
commit bf7be7f6a7c0cb4ed022ad09a684e59f290b9ce7 (HEAD -> exercise-combine-nonsequential, origin/exercise-combine-nonsequential)
Author: Martin Husbyn <[email protected]>
Date: Wed Oct 26 17:33:15 2022 +0100
top of commit sandwich
top.txt | 1 +
1 file changed, 1 insertion(+)
commit 781c5302acdc3221f1730147f8df056d347aa8e1
Author: Martin Husbyn <[email protected]>
Date: Wed Oct 26 17:32:38 2022 +0100
commit sandwich topping/filling
filling.txt | 1 +
1 file changed, 1 insertion(+)
commit 64251145b68e33683bfdb07fb1e20bd9a604e92b
Author: Martin Husbyn <[email protected]>
Date: Wed Oct 26 17:31:46 2022 +0100
bottom of commit sandwich
bottom.txt | 1 +
1 file changed, 1 insertion(+)
Combine the 'bread' commits so that we instead get an open face sandwich:
git --no-pager log --stat 7e651b879..exercise-combine-nonsequential
commit 33b291e27a19bb14fd263870b726bf668c5e6b1e (HEAD -> exercise-combine-nonsequential)
Author: Martin Husbyn <[email protected]>
Date: Wed Oct 26 17:32:38 2022 +0100
commit sandwich topping/filling
filling.txt | 1 +
1 file changed, 1 insertion(+)
commit 0aae67dc636a9a501d0167147bd6e330e13ae1b9
Author: Martin Husbyn <[email protected]>
Date: Wed Oct 26 17:31:46 2022 +0100
open face commit sandwich bread
bottom.txt | 1 +
top.txt | 1 +
2 files changed, 2 insertions(+)
Sometimes we "overcommit", and put too much into one commit. E.g. you might have started doing some cleanup/refactoring and put that in the same commit as your brand new feature, even though the changes are completely unrelated. Therefore it might sometimes be useful to split a commit into two (or three, or n) commits.
Exercise
This time, we have the branch exercise-split-commit with one commit in it, adding two files:
git --no-pager log --stat 55f2442..exercise-split-commit
commit 17a285783f599669b6294ec4457bd7b4d4c35353 (HEAD -> exercise-split-commit)
Author: Martin Husbyn <[email protected]>
Date: Wed Oct 26 17:48:25 2022 +0100
a commit that should be split
file_to_be_in_first_commit.txt | 1 +
file_to_be_in_second_commit.txt | 1 +
2 files changed, 2 insertions(+)
Split the commit on the branch, so that we have two commits, each adding one file each:
git --no-pager log --stat 55f2442..exercise-split-commit
commit 6503b60ec9f61493622e30ed2ab769fe58e228f4 (HEAD -> exercise-split-commit)
Author: Martin Husbyn <[email protected]>
Date: Wed Oct 26 17:51:57 2022 +0100
second commit
file_to_be_in_second_commit.txt | 1 +
1 file changed, 1 insertion(+)
commit 1123647354d6c64fd4fc1814920fc2342286f378
Author: Martin Husbyn <[email protected]>
Date: Wed Oct 26 17:51:44 2022 +0100
first commit
file_to_be_in_first_commit.txt | 1 +
1 file changed, 1 insertion(+)