Hi Team,
We are using “Yet Another Commit Checker” plugin in our Bitbucket Server (v 5.1.0) where we have configured the rule for commit messages to contain a valid Jira-id to prevent unknown JIRA projects, and also enforce a Commit Message REGEX.
Currently, we are facing error while trying to push our changes to the new branch, its saying ‘commit does not have issue-id’. While I am checking the details I could see that there is no issue-id for old commits (these commits have been made in the past before enabling the YACC plugin) and currently we cannot amend those commit-ids because it will change git commit history. I tried this disabling the YACC and it goes through fine and also updates my commits in BBS without any issue.
For checking the complete behavior of this plugin, i tried to enabling debug logging, but don't see YACC debug messages in atlassian-bitbucket.log.
I am sharing screenshot for old commit messages and error message both. Can you please check and help us for resolving such issue?
Please do let us know if I need to share any another logs, which will help you to understand the reason behind this issue.
Regards
Jay.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.