2,846
Customers have installed this app in at least 2,846 active instances.
2,846
Customers have installed this app in at least 2,846 active instances.
    by Mohamifor Bitbucket Server 5.2.0 - 7.4.1, Bitbucket Data Center 5.2.0 - 7.4.1 and more versions
    Versions available for Bitbucket Server 2.8.2 - 5.1.9
    Supported
    Mohami supports this app.

    Get support

    Supported
    Mohami supports this app.

    Get support

    Get it nowFree app

    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 Repos Basis

    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 Repos Basis

    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:

    • Per-project, per-repository, and global configuration
    • Require commit messages to contain valid Jira issues
    • Issue JQL matcher – can require issues to be assigned, not closed, in a certain project, etc.
    • 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:

    Mohami is an Atlassian Platinum Partner. We prioritize quality, robustness, and quick customer support. View more of our Atlassian apps here.

    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:

    • Per-project, per-repository, and global configuration
    • Require commit messages to contain valid Jira issues
    • Issue JQL matcher – can require issues to be assigned, not closed, in a certain project, etc.
    • 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:

    Mohami is an Atlassian Platinum Partner. We prioritize quality, robustness, and quick customer support. View more of our Atlassian apps here.

    Reviews for cloud

    (22)
    Sign in to write a review
    by Mark Gillespie on 2017-04-07
    Works really well for us. Ensures all commits have a JIRA.
    2 out of 2 found this review helpful
    Was this review helpful?YesNo
    by Wilber Saca on 2016-05-09
    This plugin is great, but I would like to ignore the validation if the user, group or branch not match a regex or condition. Do you have any plan about this?
    1 out of 1 found this review helpful
    Was this review helpful?YesNo
    Mohami

    All the exclusions you mentioned have since been implemented! Please refer to the documentation.

    by sailakshmi on 2016-02-05
    Hi Team, The plugin is good... I need some assistance here reg this plugin. I'm facing an issue with this plugin that when the first time i commit files commenting as per the "Commit Message Rejex",commit is done. But, when i try to commit violating the comment as per the "Commit Message Rejex" field,it is blocking the commit. I'm good till here.But,the third time i try to commit with the comment as per the "Commit Message Rejex" field,am not able to push. The push is getting rejected further irrespective of the commit message given,whether it is as per the field or not. Please help me out on the mentioned issue...
    Was this review helpful?YesNo
    Mohami

    Hi there, can you file an issue here: Submit a support request That will make it easier to help and debug than here. Thanks!

    by sandeep vb on 2015-10-20
    The plugin is cool and helpful. But I cloned repository with SSH url and I am able to push the commits without jira id. Does this plugin work for SSH protocol?
    1 out of 2 found this review helpful
    Was this review helpful?YesNo
    Mohami

    Hi there, can you file an issue here: Submit a support request That will make it easier to help and debug than here. Thanks!

    by David Raymond on 2015-08-18
    Sean, thanks for this nice plugin. I have an issue though, and although I have seen your response concerning the fact that the plugin only checks for committer in order to support merging someone else's code, it does not seem to work, at least in our use case. Consider repos A and a fork of it repos B. My colleague makes changes in repos B. I then clone repos A locally (origin points to repos A) and define another remote "dev" pointing to repos B. I fetch from "dev". In my local repository I then have my colleague's commit which is not in repos A on the server. If I push my local repos to origin (repos A), the commit fails because I am not my colleague. Is there a way around this issue. If repos B is also configured with YACC, we can argue that my colleague's commit has been validated, even though it is not in repos A. Could YACC discover this fact and allow me to push my colleague's commit to repos A? Am I misunderstanding the author/committer concept? As far as I understand my colleague is both the author and the committer of his commit in repos B, and commits are sealed objects. So when I try to push this commit to repos A, the committer is my colleague, not me. I did not do the commit. Thanks a lot, David
    Was this review helpful?YesNo
    Mohami

    Hi David!

    YACC doesn't work very well in a fork-based workflow (ie, forking 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.

    Reviews for server

    (22)
    Sign in to write a review
    by Mark Gillespie on 2017-04-07
    Works really well for us. Ensures all commits have a JIRA.
    2 out of 2 found this review helpful
    Was this review helpful?YesNo
    by Wilber Saca on 2016-05-09
    This plugin is great, but I would like to ignore the validation if the user, group or branch not match a regex or condition. Do you have any plan about this?
    1 out of 1 found this review helpful
    Was this review helpful?YesNo
    Mohami

    All the exclusions you mentioned have since been implemented! Please refer to the documentation.

    by sailakshmi on 2016-02-05
    Hi Team, The plugin is good... I need some assistance here reg this plugin. I'm facing an issue with this plugin that when the first time i commit files commenting as per the "Commit Message Rejex",commit is done. But, when i try to commit violating the comment as per the "Commit Message Rejex" field,it is blocking the commit. I'm good till here.But,the third time i try to commit with the comment as per the "Commit Message Rejex" field,am not able to push. The push is getting rejected further irrespective of the commit message given,whether it is as per the field or not. Please help me out on the mentioned issue...
    Was this review helpful?YesNo
    Mohami

    Hi there, can you file an issue here: Submit a support request That will make it easier to help and debug than here. Thanks!

    by sandeep vb on 2015-10-20
    The plugin is cool and helpful. But I cloned repository with SSH url and I am able to push the commits without jira id. Does this plugin work for SSH protocol?
    1 out of 2 found this review helpful
    Was this review helpful?YesNo
    Mohami

    Hi there, can you file an issue here: Submit a support request That will make it easier to help and debug than here. Thanks!

    by David Raymond on 2015-08-18
    Sean, thanks for this nice plugin. I have an issue though, and although I have seen your response concerning the fact that the plugin only checks for committer in order to support merging someone else's code, it does not seem to work, at least in our use case. Consider repos A and a fork of it repos B. My colleague makes changes in repos B. I then clone repos A locally (origin points to repos A) and define another remote "dev" pointing to repos B. I fetch from "dev". In my local repository I then have my colleague's commit which is not in repos A on the server. If I push my local repos to origin (repos A), the commit fails because I am not my colleague. Is there a way around this issue. If repos B is also configured with YACC, we can argue that my colleague's commit has been validated, even though it is not in repos A. Could YACC discover this fact and allow me to push my colleague's commit to repos A? Am I misunderstanding the author/committer concept? As far as I understand my colleague is both the author and the committer of his commit in repos B, and commits are sealed objects. So when I try to push this commit to repos A, the committer is my colleague, not me. I did not do the commit. Thanks a lot, David
    Was this review helpful?YesNo
    Mohami

    Hi David!

    YACC doesn't work very well in a fork-based workflow (ie, forking 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.

    Reviews for Data Center

    (22)
    Sign in to write a review
    by Mark Gillespie on 2017-04-07
    Works really well for us. Ensures all commits have a JIRA.
    2 out of 2 found this review helpful
    Was this review helpful?YesNo
    by Wilber Saca on 2016-05-09
    This plugin is great, but I would like to ignore the validation if the user, group or branch not match a regex or condition. Do you have any plan about this?
    1 out of 1 found this review helpful
    Was this review helpful?YesNo
    Mohami

    All the exclusions you mentioned have since been implemented! Please refer to the documentation.

    by sailakshmi on 2016-02-05
    Hi Team, The plugin is good... I need some assistance here reg this plugin. I'm facing an issue with this plugin that when the first time i commit files commenting as per the "Commit Message Rejex",commit is done. But, when i try to commit violating the comment as per the "Commit Message Rejex" field,it is blocking the commit. I'm good till here.But,the third time i try to commit with the comment as per the "Commit Message Rejex" field,am not able to push. The push is getting rejected further irrespective of the commit message given,whether it is as per the field or not. Please help me out on the mentioned issue...
    Was this review helpful?YesNo
    Mohami

    Hi there, can you file an issue here: Submit a support request That will make it easier to help and debug than here. Thanks!

    by sandeep vb on 2015-10-20
    The plugin is cool and helpful. But I cloned repository with SSH url and I am able to push the commits without jira id. Does this plugin work for SSH protocol?
    1 out of 2 found this review helpful
    Was this review helpful?YesNo
    Mohami

    Hi there, can you file an issue here: Submit a support request That will make it easier to help and debug than here. Thanks!

    by David Raymond on 2015-08-18
    Sean, thanks for this nice plugin. I have an issue though, and although I have seen your response concerning the fact that the plugin only checks for committer in order to support merging someone else's code, it does not seem to work, at least in our use case. Consider repos A and a fork of it repos B. My colleague makes changes in repos B. I then clone repos A locally (origin points to repos A) and define another remote "dev" pointing to repos B. I fetch from "dev". In my local repository I then have my colleague's commit which is not in repos A on the server. If I push my local repos to origin (repos A), the commit fails because I am not my colleague. Is there a way around this issue. If repos B is also configured with YACC, we can argue that my colleague's commit has been validated, even though it is not in repos A. Could YACC discover this fact and allow me to push my colleague's commit to repos A? Am I misunderstanding the author/committer concept? As far as I understand my colleague is both the author and the committer of his commit in repos B, and commits are sealed objects. So when I try to push this commit to repos A, the committer is my colleague, not me. I did not do the commit. Thanks a lot, David
    Was this review helpful?YesNo
    Mohami

    Hi David!

    YACC doesn't work very well in a fork-based workflow (ie, forking 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.

    Cloud Pricing

    Server Pricing

    Data Center Pricing

    Mohami provides support for this app.

    Mohami provides support for this app.

    Vendor support resources

    Documentation

    Find out how this app works.

    Vendor support resources

    Documentation

    Find out how this app works.

    Versions

    Version 1.25.0 Bitbucket Server 5.2.0 - 7.4.1 Released 2020-07-23

    Summary

    Check edits made through the built-in editor

    Details

    • YACC-93 - Apply exclusions before checking author name and email
    • YACC-110 - Check edits made via the Bitbucket web editor
    • Apply a timeout to regex matching to prevent catastrophic backtracking

    Versions

    Version 1.25.0 Bitbucket Data Center 5.2.0 - 7.4.1 Released 2020-07-23

    Summary

    Check edits made through the built-in editor

    Details

    • YACC-93 - Apply exclusions before checking author name and email
    • YACC-110 - Check edits made via the Bitbucket web editor
    • Apply a timeout to regex matching to prevent catastrophic backtracking

    Installation

    1. Log into your Bitbucket instance as an admin.
    2. Click the admin dropdown and choose Add-ons. The Manage add-ons screen loads.
    3. Click Find new apps or Find new add-ons from the left-hand side of the page.
    4. Locate Yet Another Commit Checker via search. Results include app versions compatible with your Bitbucket instance.
    5. Click Install to download and install your app.
    6. 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.

    1. Log into your Bitbucket instance as an admin.
    2. Click the admin dropdown and choose Add-ons. The Manage add-ons screen loads.
    3. Click Find new apps or Find new add-ons from the left-hand side of the page.
    4. Locate Yet Another Commit Checker via search. Results include app versions compatible with your Bitbucket instance.
    5. Click Install to download and install your app.
    6. 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.

    Similar apps