Add List All Files Changed Between Two Branches as a git til

README.md

@@ -7,7 +7,7 @@ variety of languages and technologies. These are things that don't really
 warrant a full blog post. These are mostly things I learn by pairing with
 smart people at [Hashrocket](http://hashrocket.com/).
 
-_476 TILs and counting..._
+_477 TILs and counting..._
 
 ---
 
@@ -128,6 +128,7 @@ _476 TILs and counting..._
 - [Intent To Add](git/intent-to-add.md)
 - [Interactively Unstage Changes](git/interactively-unstage-changes.md)
 - [Last Commit A File Appeared In](git/last-commit-a-file-appeared-in.md)
+- [List All Files Changed Between Two Branches](git/list-all-files-changed-between-two-branches.md)
 - [List Different Commits Between Two Branches](git/list-different-commits-between-two-branches.md)
 - [List Filenames Without The Diffs](git/list-filenames-without-the-diffs.md)
 - [List Most Git Commands](git/list-most-git-commands.md)

git/list-all-files-changed-between-two-branches.md

@@ -0,0 +1,23 @@
+# List All Files Changed Between Two Branches
+
+The `git-diff` command can help with finding all files that have changed
+between two branches. For instance, if you are at the `HEAD` of your current
+feature branch and you'd like to see the list of files that have changed
+since being in sync with the `master` branch, you'd formulate a command like
+the following:
+
+```bash
+$ git diff --name-only master
+```
+
+The `--name-only` flag is important because it cuts out the rest of the
+non-essential output.
+
+You'll want to list the _older_ branch first and the current branch second
+as a way of showing what has changed from the original branch to get to the
+current branch.
+
+Though the example shows the use of _branches_ any git reference can be used
+to see what has changed between two commits.
+
+See `man git-diff` for more details.