Better Commit Policy for Bitbucket
Verify the changes (branches, tags, commits) committed to Bitbucket against configurable rules
Work securely with check-in requirements
Verify the commit message, the changed files, the committer, the affected branches and tags before a commit is accepted.
Combine conditions and limit those to branches or directories.
Easy change control, fast code reviews & audits
Implement processes for compliance with industry standards & regulations.
Establish development workflows for consistent repository, code & history.
Enforce traceability between Jira issues and code changes.
Better Commit Policy checks the changes committed to Bitbucket repositories against a set of configurable rules (the commit policy). It does so by integrating the Better Commit Policy for Jira with Bitbucket. When the policy is not satisfied, the commit is rejected. Rejected commits can then be "fixed" and re-committed.
- Improved change control over your source code
- Easier compliance with regulations (story)
- Faster code reviews
- Bi-directional traceability between source code changes and Jira issues
- Clear commit history
- Commit to issue link
- Commit message
- Change files
- Branch name
- Branch to issue link
- Tag name
- ... and more!
Unlike the alternatives, this app:
- verifies changes locally ★before★ those are committed! 🔥
- verifies pull requests
- is supported
- ... for more see the detailed comparison →
☛ Connect Bitbucket, Slack, Twilio, email, CI/CD and custom scripts to Jira workflows with our DevOps automation app!
Privacy and security
Manage commit policies centrally in Jira. Commit policies can be shared by multiple Jira projects and multiple Bitbucket repositories for ultimate flexibility. See: http://bit.ly/2AHmO0R