Better Commit Policy for Jira Server/Data Center: Feature Requests
Ideas and requests for new features. Suggest ideas. Vote for the best. See what's planned.
- Add support for triggering automations by commits ("smart commits")
- Add a "repository" rule scope limiting feature
- Add "commit message must match a pattern" tag condition type
- Detect "existing" state of commits in a Bitbucket Pull Request even if the commits only exist in the fork (source repo)
- Add support for git "core.hooksPath" configuration
- Customizable rejection message header and footer decoration
- Policy should provide an "all rule types" or "at least one rule type" selector
- Make "Exactly one issue key must be mentioned in the commit message" messages more expressive
- Add "File size must be less than" commit condition type
- Add MinGW support for git client side hooks
- Implement hook scripts in Go language
- Support for CVS
- Add Python 2.6 support to hook scripts
- Only accept signed commits (with Git)
- Support for ClearCase
- Policy should provide an "all rules" or "at least one rule" selector
- Support for SVN properties
- Support for Team Foundation Server (TFS)
- Support Gitblit hooks
- Implement client side hook script for Mercurial
- Allow creating hook script packages without letting the user access the policy details
- Support for verifying changes made in Bitbucket's built-in editor
- Add a "commit message must contain a username" condition
- Support Gerrit