Hook to validate and block commits according to configured policies. Easily enforce Jira workflows
Hook to validate and block commits according to configured policies. Easily enforce Jira workflows
Hook to validate and block commits according to configured policies. Easily enforce Jira workflows
Enforce Workflows and High Quality Commit History
Highly Configurable and Customizable
Configurable on a Global, Project, or Repo Level
Per-project, per-repository, and global configurations allow you to enforce company best practices like requiring commit messages to match regexes, or to contain Jira issues that are in the correct status.
Customize your error messages to teach developers about best practices. Require issues to be assigned, not closed, or in a certain project to be accepted on commit. Exclude branches from commit policies.
Use a JQL query to check and enforce any field of a Jira issue, including custom fields. Rules can be inherited on a project or global basis.
Enforce Workflows and High Quality Commit History
Highly Configurable and Customizable
Configurable on a Global, Project, or Repo Level
Per-project, per-repository, and global configurations allow you to enforce company best practices like requiring commit messages to match regexes, or to contain Jira issues that are in the correct status.
Customize your error messages to teach developers about best practices. Require issues to be assigned, not closed, or in a certain project to be accepted on commit. Exclude branches from commit policies.
Use a JQL query to check and enforce any field of a Jira issue, including custom fields. Rules can be inherited on a project or global basis.
More details
Enforce your workflows and maintain high quality commit history with Yet Another Commit Checker. Easily configure a variety of checks and enable them globally or for specific projects and repositories.
✅ Feature highlights:
- Repository, project, and global configuration
- Require commit messages to contain valid Jira issues
- Issue JQL matcher – can require issues to be in progress, in a certain project, etc.
- Use either as a pre-receive hook or as a merge check
- Require committer name and email to match Bitbucket user
- Require commit messages to match regex
- Validate branch names
- Customizable errors
😀 More Bitbucket apps you’ll like:
- Prevent accidentally exposing sensitive data with Security for Bitbucket
- Host documentation or any static website directly from a repository, with Pages for Bitbucket
- Easily create and share code snippets in Bitbucket Server with Snippets for Bitbucket
Mohami is an Atlassian Platinum Partner.
More details
Enforce your workflows and maintain high quality commit history with Yet Another Commit Checker. Easily configure a variety of checks and enable them globally or for specific projects and repositories.
✅ Feature highlights:
- Repository, project, and global configuration
- Require commit messages to contain valid Jira issues
- Issue JQL matcher – can require issues to be in progress, in a certain project, etc.
- Use either as a pre-receive hook or as a merge check
- Require committer name and email to match Bitbucket user
- Require commit messages to match regex
- Validate branch names
- Customizable errors
😀 More Bitbucket apps you’ll like:
- Prevent accidentally exposing sensitive data with Security for Bitbucket
- Host documentation or any static website directly from a repository, with Pages for Bitbucket
- Easily create and share code snippets in Bitbucket Server with Snippets for Bitbucket
Mohami is an Atlassian Platinum Partner.
Reviews for cloud
(25)Sign in to write a review
All the exclusions you mentioned have since been implemented! Please refer to the documentation.
Hi there, can you file an issue here: Submit a support request That will make it easier to help and debug than here. Thanks!
I think you may be trying to push two commits. The first commit violates the message regex, the second commit is OK. In order to push you will have to update the commit message of the first commit (e.g by using "git rebase -i" or "git commit --amend") so that it conforms to the regex.
Hi there, can you file an issue here: Submit a support request That will make it easier to help and debug than here. Thanks!
The plugin definitely works for SSH checkouts. I think you may be using an "access key" rather than a user SSH key -- this creates commits under a "Service User". If this is the case, make sure the "Exclude Service User Commits" option is not enabled.
Hi David!
In the example that you give, the commits from your colleague in repo B are brand new with respect to repo A, so YACC attempts to validate the committer against the person who is pushing (you).
The next version of YACC will contain an option to relax user name and author checks in order to support this workflow. See YACC-57: Allow any valid commit author to support fork workflow
Reviews for server
(25)Sign in to write a review
All the exclusions you mentioned have since been implemented! Please refer to the documentation.
Hi there, can you file an issue here: Submit a support request That will make it easier to help and debug than here. Thanks!
I think you may be trying to push two commits. The first commit violates the message regex, the second commit is OK. In order to push you will have to update the commit message of the first commit (e.g by using "git rebase -i" or "git commit --amend") so that it conforms to the regex.
Hi there, can you file an issue here: Submit a support request That will make it easier to help and debug than here. Thanks!
The plugin definitely works for SSH checkouts. I think you may be using an "access key" rather than a user SSH key -- this creates commits under a "Service User". If this is the case, make sure the "Exclude Service User Commits" option is not enabled.
Reviews for Data Center
(25)Sign in to write a review
All the exclusions you mentioned have since been implemented! Please refer to the documentation.
Hi there, can you file an issue here: Submit a support request That will make it easier to help and debug than here. Thanks!
I think you may be trying to push two commits. The first commit violates the message regex, the second commit is OK. In order to push you will have to update the commit message of the first commit (e.g by using "git rebase -i" or "git commit --amend") so that it conforms to the regex.
Hi there, can you file an issue here: Submit a support request That will make it easier to help and debug than here. Thanks!
The plugin definitely works for SSH checkouts. I think you may be using an "access key" rather than a user SSH key -- this creates commits under a "Service User". If this is the case, make sure the "Exclude Service User Commits" option is not enabled.
Cloud Pricing
Server Pricing
Data Center Pricing
| 10 users$10 | 25 users$250 | 50 users$450 | 100 users$830 | 250 users$1,800 | 500 & upAdditional pricing details |
| 25 users$250/year | 50 users$450/year | 100 users$830/year | 250 users$1,800/year | 500 users$2,800/year | 1000 & upAdditional pricing details |
Pricing FAQ
- How does server app pricing work?
Server products and apps are hosted on your servers. This app is sold as a perpetual license, and the purchase price includes 12 months of maintenance (support and version updates).
You can renew maintenance after 12 months at 50% of the current purchase price. You can upgrade the tier of your Atlassian product and app licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).
If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.
- How do I determine my server pricing?
Apps are billed based on the number of users in your Atlassian product. The app tier should match the licensed user tier of the Atlassian product. For example, if you have a Confluence license for 500 users, you should purchase the 500-user tier for apps. Even if fewer users want to use the app than your Atlassian product license, the two licenses should match exactly.
- Can I install this app in a Data Center product?
Yes, this app has a Data Center approved version. If you're using a Data Center product, you should install the Data Center version of the app.
- What type of license do I need if I'm using this app in a Data Center product?
Because this app has a Data Center approved version, you should purchase a Data Center license for the app.
If you already own a server license for this app, you can continue using the server license in your Data Center product for a limited period of time.
- Do you offer academic, community, or open-source licenses for server apps?
For server apps, academic licenses are available at a 50% discount if you have an academic license for your Atlassian product.
Community and open-source licenses are available for server apps. Learn more about community and open source licenses.
- Can I extend my free trial?
For server apps, you can extend your app trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the app listing in UPM from your Atlassian product, and you're all set.
- How can I buy apps for my legacy Jira Server or Confluence Server license?
If you own a legacy Jira Server Unlimited (100+ users) or Confluence Server Unlimited (2000+ users) license purchased in 2012 or earlier, legacy app pricing is no longer available. You have two options for app purchasing:
- Purchase the app at the non-legacy Unlimited (10000+ users) tier.
- Renew your Jira or Confluence license at a non-legacy tier, then purchase the app at the same tier.
Pricing FAQ
- How does Data Center app pricing work?
Data Center apps are sold as an annual subscription. You are eligible for support and version updates as long as your subscription is active.
If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.
- How do I determine my Data Center pricing?
Apps are billed based on the number of users in your Atlassian product. The app tier should match the licensed user tier of the Atlassian product. For example, if you have a Confluence license for 500 users, you should purchase the 500-user tier for apps. Even if fewer users want to use the app than your Atlassian product license, the two licenses should match exactly.
- Can I install this app in a Data Center product?
Yes, this app has a Data Center approved version. If you're using a Data Center product, you should install the Data Center version of the app.
- What type of license do I need if I'm using this app in a Data Center product?
Because this app has a Data Center approved version, you should purchase a Data Center license for the app.
If you already own a server license for this app, you can continue using the server license in your Data Center product for a limited period of time.
- Do you offer academic, community, or open-source licenses for Data Center apps?
For Data Center apps, academic licenses are available at a 50% discount if you have an academic license for your Atlassian product.
Community and open-source licenses are not available for Data Center apps. Learn more about community and open source licenses.
- Can I extend my free trial?
For Data Center apps, you can extend your app trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the app listing in UPM from your Atlassian product, and you're all set.
Mohami Atlassian Apps (an Appfire company) provides support for this app.
Mohami Atlassian Apps (an Appfire company) provides support for this app.
Vendor support resources
Find out how this app works.
Vendor support resources
Find out how this app works.
Versions
Version 2.0.8 • Bitbucket Server 5.2.0 - 7.11.2 • Released 2021-02-05
Summary
Improved error messages
Details
- YACC-280 -- Less confusing error message when encountering permissions errors
Versions
Version 2.0.8 • Bitbucket Data Center 5.2.0 - 7.11.2 • Released 2021-02-05
Summary
Improved error messages
Details
- YACC-280 -- Less confusing error message when encountering permissions errors
Installation
- Log into your Bitbucket instance as an admin.
- Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
- Click Find new apps or Find new add-ons from the left-hand side of the page.
- Locate Yet Another Commit Checker via search. The appropriate app version appears in the search results.
- Click Try free to begin a new trial or Buy now to purchase a license for Yet Another Commit Checker. You're prompted to log into MyAtlassian. Yet Another Commit Checker begins to download.
- Enter your information and click Generate license when redirected to MyAtlassian.
- Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your Bitbucket instance.
To find older Yet Another Commit Checker versions compatible with your instance, you can look through our version history page.
- Log into your Bitbucket instance as an admin.
- Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
- Click Find new apps or Find new add-ons from the left-hand side of the page.
- Locate Yet Another Commit Checker via search. The appropriate app version appears in the search results.
- Click Try free to begin a new trial or Buy now to purchase a license for Yet Another Commit Checker. You're prompted to log into MyAtlassian. Yet Another Commit Checker begins to download.
- Enter your information and click Generate license when redirected to MyAtlassian.
- Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your Bitbucket instance.
To find older Yet Another Commit Checker versions compatible with your instance, you can look through our version history page.
Similar apps
