Use descriptive commit messages that include issue tracking information, such as a Jira issue, for example, that clearly describe the intent of the commit. Avoid writing commit messages that are vague, such as Fixed bug or Wrapped up, as these types of commit messages are not useful and are not helpful to developers later on.
Here is a sample descriptive commit message [DEV-1003] added a new navigation link to the Parts Supply list. A test case for the new navigation was also added. This is clearly more descriptive. Additionally, in Jira, when you provide an issue such as DEV-1003, it will create a link in the Jira issue that references the work on this issue. Also, if you create a pull ...
