RELEASE NOTES

You've studied the Git/hacks and built a ton of features, fixes, and updates to your codebase in a sprint worthy of Usain Bolt

. Now it's time to create some release notes - which in the tradition of open source is stored in the RELEASE_NOTES file of your project.

Since your team follows the best practices of writing good commit comments and also creating appropriate branches and pull requests, then it's a simple matter of letting git tell you what's in the release. Of course you can amend or add to it as needed.

First, study git/log for how to use the log command.

find the last parent branch see Git/hacks
do a git log --stat or git log --pretty between the prior branch and HEAD

--no-merges
Show the whole commit history, but skip any merge commits so that the Release Notes are not cluttered with workflow items.