In this page

Overview

This page collects various articles that demonstrate how to use Better Commit Policy Connector for Bitbucket Data Center for the best results. Most reads are about 5 minutes.

Important: subscribe to the Midori Newsletter so that you will be automatically notified in a monthly email when we publish new tutorials.

For tutorials that are created for starters or focus on one use case, check out the tutorial videos.

Tutorials

The articles in this section include useful guides for frequent use cases, case studies contributed by power-users, integration how-to's, and practical tips to solve concrete business problems.

Git 50/72: the rule of well formed Git commit messages (2026 guide)

The Git 50/72 rule defines how long a commit message subject and body should be, and it is the most widely adopted standard for readable, traceable Git history. Bitbucket Cloud has no native way to enforce it. This guide explains the rule, why it exists, and how to enforce it automatically using policy-as-code with Better Commit Policy.

5 ways to speed up code reviews with Git, Mercurial and Subversion

Code reviews and code commit best practices under Git, Mercurial (and Subversion to some extent) are ever-green and controversial topics in the DevOps community. In this blog post we make the case for a well-thought out code change practice and try to prove that if it's done right and supported with the right apps, then following the best practice is not only easy, but it improves your practices as a developer. Read this blog post and feel the change, regardless which side of the code review are you.

External articles

In this section you can find articles written by Atlassian Solution Partner teams, using their unique knowledge, occasionally in their native language. These are hosted at the partner's own website.

How to speed up code reviews

(at Atlassian)

Ask anyone in the DevOps community and chances are, they will tell you that code review is time-consuming and frequently boring, but it's a critical phase of the software development process. What they mention less often is that the long back and forths with developers can be spared if you first get your commits right.