Voila!

Always prefix your commit message with your JIRA ID for tracking purpose, no matter if you are committing in the feature branch or not.  Linking git commit messages from Jira tickets is important for several reasons, such as: It creates a traceable link between the code changes and the Jira issues, which can help with tracking the progress, status, and history of the project. It enables the developers and the stakeholders to see the branches, commit messages, and pull requests related to the Jira issues, which can improve the communication and collaboration among the team members. It allows the developers to easily reference and navigate to the Jira issues from BitBucket, which can save time and effort. It ensures that the code changes are aligned with the requirements and expectations of the users or clients, which can enhance the quality and performance of the software products. Template JIRA-ID : Your commit message will come here Figure 1: Template for commit message Example K...

To understand the process involved in it, we need to first understand the terminologies that is being used in the git. Suppose you have committed your code in Git repository. Now when you select the particular commit, then you will see something like this TK-34164 e2e test cases added Commit: 96f17e85e5b76cff8a6a0332c4f22d10aca3aec6 [96f17e8] Parents: 56a575c5b8 Author: Abhishek Kumar Date: 3 January 2017 at 18:52:06 IST Labels: HEAD -> feature/TK-34164-configure-robot-framework-into Here at line  #1  is custom message for the commit, after that at line  #2  you see a commit-id which is 40 characters long hexadecimal string (SHA-1) and it's short version in square bracket which is 7 characters long.  SHA-1  (Secure Hash Algorithm 1) produces a 160-bit (20-byte) hash value known as a message digest. A SHA-1 hash value is typically rendered as a hexadecimal number, 40 digits long. This  commit-id  is 160-bit SHA-1 hash, uniquely rep...