Support for verifying changes made in Bitbucket's built-in editor Ferenc Nagy September 12, 2019 14:11 Follow Have more questions? Submit a request 2 Comments Date Votes 0 YooRim Won February 21, 2019 01:51 If someone enters the wrong "issue key" in the commit message of bitbucket or "commit" without entering the "issue key", we want show warning message and restrict "commit" in Bitbucket. 0 Aron Gombas September 12, 2019 14:11 Quick update: we tried to solve this in the 4.2.0 app version. Unfortunately, when a hook rejects a change made through the built-in editor, Bitbucket wants the user to create a new branch for his changes and also a PR from that branch to the branch where the file was originally opened from for editing. This is because Bitbucket expects that the only reason for the rejection is the lack of the "write" permission on the target branch. This is, obviously, a wrong assumption. We already reported this to Atlassian, hopefully it will be fixed soon. Until then, we decided not to release this feature as the UX and the interaction is really awkward. Please sign in to leave a comment.