In this page
Git 50/72: the rule of well formed Git commit messages
5 ways to speed up code reviews with Git, Mercurial and Subversion
How to install pre-receive hooks in GitLab
How to prepare for GitHub Enterprise code reviews
How to speed up code reviews
Better Commit Policy で Jira Software と Bitbucket Server との連携を強化
Webinar recap and Q&A: How commit policies enable end-to-end traceability and faster code reviews
This page collects various articles that demonstrate how to use the Better Commit Policy app with 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.
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.
Easy-to-understand commit messages in version control systems are important to maintain a clear project history. Who will remember after six months what a two-word message (e.g.: Fixed bugs) meant? Similarly, a novel about the solution and the shining talents of the developer doesn't help understanding the original intent either. The 50/72 rule is about balancing and sharing the right amount of information in commit messages to build a clean code history. Using it in your team is not wishful thinking: learn how you can take advantage of it in a quick and painless way.
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.
Better Commit Policy 4.3.0 brings popular new integrations and features to suggest Jira issues to include in your commit message or share your commit policy among Jira projects. One of the highly requested integrations is between GitLab and Jira. Read how Better Commit Policy for Jira 4.3.0 delivered this!
Keeping a traceable and audit-proof source code change history should not be a hassle for any developer team. If you are using GitHub Enterprise and Jira together, you can count on the power of pre-receive hooks by Better Commit Policy for Jira to speed up code reviews. Build a robust commit policy system to guard your GitHub Enterprise repositories!
In this section you can find articles written by Atlassian Solution Partner teams, using their unique knowledge, eventually in their native language. These are hosted at the partner's own website.
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.
Jira Software と Bitbucket Server とを連携させるメリットの 1 つとして、スマート コミット機能があげられます。スマート コミットとは、コミット メッセージに特定の文字列を含めることで、さまざまな操作を行える機能です。このスマート コミットを利用することで、Jira 課題に対してコメントの作成、作業時間の記録、ステータスの変更などを行えます。ソース コードの修正を JIRA で管理している場合、スマート コミットを活用することでトレーサビリティの向上を図ることが可能です。 スマート コミットの問題点は、コミット メッセージの内容確認がコミッター自身に委ねられていることです。したがって、コミット メッセージに含めるべき情報をうっかり入力し忘れることも考えられます。この問題を解決するのが、今回紹介する Commit Policy Plugin for Jira です。
You can find recaps of past webinars in this section. Each recap comes with the webinar's video recording, the slides, the questions and the answers.
Thank you all who joined us live in our "How commit policies enable end-to-end traceability and faster code reviews" webinar on November 28. If you missed it, or want to grab the presentation slides, then here is a quick recap for you. You can also find the video recording in this recap blog post, plus the questions that were answered in the Q&A section.