Back

Explore Courses Blog Tutorials Interview Questions
0 votes
2 views
in DevOps and Agile by (29.3k points)

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 are 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).

In any case, we're starting to build some momentum, I thought it would be really good to be able to show people what has changed since the last release. 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.

I tried googling "git changelog" and "git manage changelog" but I didn't find anything that really talked about the workflow of code changes and how that coincides with the changelog

Is there a standard approach that I am missing, or is this an area where everybody does their own thing?

1 Answer

0 votes
by (50.2k points)

You can generate logs in a gorgeous manner by using the following commands:

git log --oneline --decorate

This will decorate the log for you. 

If you want logs with colours to make prettier you could use:

git log --oneline --decorate --color

And --graph option will show you the logs in a graphical manner. These are good ways to manage a changelog using git.

For more information refer: https://git-scm.com/docs/git-log#Documentation/git-log.txt---decorateshortfullautono 

Browse Categories

...