title: What are some good ways to manage a changelog using Git?
body: <p>I've been using Git for a while now, and I recently started using it to tag my releases so that I could more easily keep track of changes and be able to see which version each of our clients is running (unfortunately the code currently mandates that each client have their own copy of the PHP site; I'm changing this, but it's slow-going).</p>
  <p>In any case, we're starting to build some momentum, and I thought it would be really good to be able to show people what has changed since the last release. The problem is, I haven't been maintaining a changelog, because I don't have a good idea of how to go about it. For this particular time, I can run through the log and manually create one, but that will get tiring very quickly.</p>
  <p>I tried googling &quot;git changelog&quot; and &quot;git manage changelog&quot;, but I didn't find anything that really talked about the workflow of code changes and how that coincides with the changelog. We're currently following <a href="http://reinh.com/blog/2009/03/02/a-git-workflow-for-agile-teams.html" rel="noreferrer">Rein Henrichs' development workflow</a> and I would love something that went along with that.</p>
  <p>Is there a standard approach that I am missing, or is this an area where everybody does their own thing?</p>