In this page
This page is specifically for Git repositories managed by the Bitbucket Server platform!
If you use Git, but not Bitbucket Server, see the general Git guide instead.
Working with Bitbucket Server commit policies
Bitbucket Server builds on the top of the Git version control system, extending that with repository-, user- and permission management capabilities and with other high-level functionality. Therefore, everything written in the general Git guide also applies to Git repositories managed by Bitbucket Server.
In the Better Commit Policy app's context, the only difference between using Git alone and Git with Bitbucket Server is how you install the commit hooks.
The hook installation process is detailed in the next section, but that is relevant to you only if you are an administrator of the Bitbucket Server instance. If you are a developer (making commits and pushing those to Bitbucket Server), you can use your Git client exactly the same way regardless if the server runs Git alone or Git with Bitbucket Server.
In both cases, make absolutely sure you read the Git guide. It explains fixing rejected commits, working with Git features (branching, merging, rebasing, tagging, cherry-picking) and helps to resolve common problems.
Installing Bitbucket Server commit hooks
To ease implementing commit and pull request verification in Bitbucket Server, Midori offers a separate Bitbucket app intutitively called Better Commit Policy for Bitbucket. It is free and can be installed to Bitbucket without generating any license.
After you install that app and link Bitbucket with an application link to a Jira instance (where Better Commit Policy for Jira is installed), then the commit verification functionality becomes available in Bitbucket with a fully native experience!
For this, follow the guides in the Better Commit Policy for Bitbucket documentation.
Ask us any time.