
Reject commits to a repository based on configurable rules
Reject commits to a repository based on configurable rules
Reject commits to a repository based on configurable rules
Yet Another Commit Checker is easily configured.
Fun and lighthearted errors make it clear what needs to be fixed!
Any Jira Query can be used in YACC to validate issues.
Yet Another Commit Checker is easily configured.
Fun and lighthearted errors make it clear what needs to be fixed!
Any Jira Query can be used in YACC to validate issues.
More details
Yet Another Commit Checker is a Bitbucket Server plugin that allows you to reject commits to a repository based on configurable rules. Its main feature is requiring commit messages to contain a valid Jira issue, and optionally requiring issues to match a JQL query. For example, making sure issues are assigned and in progress.
Features:
- Per-project, per-repository, and global configuration
- Require committer name and email to match user
- Require commit messages to match regex
- Require commit message to contain valid Jira issue ids
- Issue JQL matcher to validate Jira issue against. Require issues to be assigned, not closed, in a certain project, etc. The possibilities are endless!
- No extra Jira configuration is required. Will use existing Jira Application Link!
- Validate branch names
- Customizable errors
- Branch friendly! Only new commits are checked.
See https://github.com/sford/yet-another-commit-checker for more information and source code.
More details
Yet Another Commit Checker is a Bitbucket Server plugin that allows you to reject commits to a repository based on configurable rules. Its main feature is requiring commit messages to contain a valid Jira issue, and optionally requiring issues to match a JQL query. For example, making sure issues are assigned and in progress.
Features:
- Per-project, per-repository, and global configuration
- Require committer name and email to match user
- Require commit messages to match regex
- Require commit message to contain valid Jira issue ids
- Issue JQL matcher to validate Jira issue against. Require issues to be assigned, not closed, in a certain project, etc. The possibilities are endless!
- No extra Jira configuration is required. Will use existing Jira Application Link!
- Validate branch names
- Customizable errors
- Branch friendly! Only new commits are checked.
See https://github.com/sford/yet-another-commit-checker for more information and source code.
Reviews for cloud
(22)Sign in to write a review
Hi there, can you file an issue here: https://github.com/sford/yet-another-commit-checker/issues That will make it easier to help and debug then here. Thanks!

Hi David!
YACC doesn't work very well in a fork-based workflow (ie, cloning the repository when making a change rather than just creating a branch in the existing repository). :-( 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). YACC can't distinguish between a commit from another repository committed by someone else, to a commit that simply has the wrong committer information due to git being misconfigured.
It might be feasible to somehow code YACC to check other repositories to see if the commit is present elsewhere, but that isn't how YACC currently operates. Sorry :-(
Sean
Reviews for server
(22)Sign in to write a review
Hi there, can you file an issue here: https://github.com/sford/yet-another-commit-checker/issues That will make it easier to help and debug then here. Thanks!

Hi David!
YACC doesn't work very well in a fork-based workflow (ie, cloning the repository when making a change rather than just creating a branch in the existing repository). :-( 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). YACC can't distinguish between a commit from another repository committed by someone else, to a commit that simply has the wrong committer information due to git being misconfigured.
It might be feasible to somehow code YACC to check other repositories to see if the commit is present elsewhere, but that isn't how YACC currently operates. Sorry :-(
Sean
Reviews for Data Center
(22)Sign in to write a review
Hi there, can you file an issue here: https://github.com/sford/yet-another-commit-checker/issues That will make it easier to help and debug then here. Thanks!

Hi David!
YACC doesn't work very well in a fork-based workflow (ie, cloning the repository when making a change rather than just creating a branch in the existing repository). :-( 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). YACC can't distinguish between a commit from another repository committed by someone else, to a commit that simply has the wrong committer information due to git being misconfigured.
It might be feasible to somehow code YACC to check other repositories to see if the commit is present elsewhere, but that isn't how YACC currently operates. Sorry :-(
Sean
Cloud Pricing
Server Pricing
Data Center Pricing
Sean Ford provides support for this app.
Sean Ford provides support for this app.
Vendor support resources
Find out how this app works.
Community discussions connect you to the vendor and other customers who use this app.
Atlassian-hosted discussions connect you to other customers who use this app.
Vendor support resources
Find out how this app works.
Community discussions connect you to the vendor and other customers who use this app.
Atlassian-hosted discussions connect you to other customers who use this app.
Versions
Version 1.23 • Bitbucket Server 5.2.0 - 5.16.1 • Released 2019-01-11
Summary
Data Center Support
Details
Re-enable support for Bitbucket Data Center.
Versions
Version 1.23 • Bitbucket Data Center 5.2.0 - 5.16.1 • Released 2019-01-10
Summary
Data Center Support
Details
Re-enable support for Bitbucket Data Center.
Installation
- Log into your Bitbucket instance as an admin.
- Click the admin dropdown and choose Add-ons. 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. Results include app versions compatible with your Bitbucket instance.
- Click Install to download and install your app.
- You're all set! Click Close in the Installed and ready to go dialog.
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 Add-ons. 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. Results include app versions compatible with your Bitbucket instance.
- Click Install to download and install your app.
- You're all set! Click Close in the Installed and ready to go dialog.
To find older Yet Another Commit Checker versions compatible with your instance, you can look through our version history page.