Yet Another Commit Checker joins the Mohami app suite

I’m happy to announce that the #1 Commit hook Yet Another Commit Checker has now joined the Mohami family.

Yet Another Commit Checker has helped 3000 teams around the world enforce workflows and high quality commit history, facilitating best practices that teams need.

Mohami has been working on YACC for the past two months, and we’ve already released two updates that delivered bug fixes that users have been requesting for over 3 years:

• YACC-110 — Check edits made via the Bitbucket web editor
• YACC-93 — Apply exclusions before checking author name and email

Unfortunately prior to our acquisition the app had become stagnant, with delayed compatibility updates, lack of new features, and built-up technical debt. The Bitbucket Data Center compatible version of YACC was released more than a year after the start of Atlassian’s Data Center program. Atlassian now requires that Data Center certification be done every 6 months; this hinders open source apps even further by adding extensive recurring work to keep apps on the marketplace. A number of other marketplace changes, like the security program requirements, and the EULA requirements, have made open source app development in the Atlassian marketplace unsustainable.

By acquiring the app, our goal is to add highly requested features, provide excellent and timely customer support, improve documentation, and apply bug-fixes immediately. But to do that, we need to be able to justify devoting our resources to the app.

From this point forward, we’re going to be transitioning all new updates to YACC to paid. With that said, we’re releasing version 2.0.0 of YACC today! This update is packed with some of the most requested features that YACC has had over its lifetime, as well as a significant number of bugfixes:

Features + Improvements

• YACC-264 YACC has now been added as a merge check, allowing checks to be performed when merging PR’s rather than when pushing new code.
• YACC-3 New option to specify a user to use for all Jira queries. Administrators can now configure the impersonation in the global settings. This helps with various permissions issues (e.g. a user commit mentions an issue they don’t have permissions to view, or CI commits using an API key so there’s no corresponding Jira account).
• YACC-259 Updated UI to follow new atlassian branding schemes, added web items to access global settings so users no longer have to access settings through the app management page.
• YACC-209 New option to require that commit messages and branch names are referencing the same Jira issue.

Bugfixes

• YACC-260 Fixed a bug where the branch exclusion regex was not being applied on branch creation.
• YACC-59 Fixed a bug where commit message regex fails for long commit messages (>2321 characters). YACC will now tell you to either reduce the length of your commit message or write a more efficient regex.
• YACC-256 Fixed a bug where YACC didn’t check merge commits created by a pull request.
• YACC-51 Fixed a bug where the custom branch name error message text was not displayed for UI changes.
• YACC-69 Fixed a permissions issue where users were able to edit the global configuration as a non-admin.
• YACC-269 Fixed a bug where “Ignore Unknown Jira Project Keys” option was allowed to be switched on when not checking for Jira issues.
• YACC-254 Fixed a bug where the custom message formatting was indenting the first lines but not the other lines.

We’ve also given the app a new logo:

We’re excited about the future of Yet Another Commit Checker. We’ve got a ton of features planned, and we hope all of you are as excited as we are.