Tracking application changes without a version control system is like finding a needle in a haystack. We have seen how to use GitLab to track application changes in Chapter 5, Version Control. Whenever bugs are reported by testers, we use a bug tracker such as Bugzilla to track the life cycle of a bug—from identifying it until the fix is released to production. When a new bug or feature is added to the bug tracker, it is assigned to a developer and the developer starts working on that fix or new feature. Code changes are tracked in Git repositories when developers commit changes to the respective feature branch. The develop branch commit message should contain the bug ID to identify the changes done with respect to a particular bug or feature.
If a new feature is added or an issue is fixed, developers can add meaningful commit messages...
