Apply Push rules commit messages restriction to protected branches only
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Currently, the Push rules commit messages restriction feature works globally across all branches. Is it not possible to restrict only some branches (probably protected branches).
Problem to solve
As Rachel (Release Manager), I would like all the commits in the protected ("main") branches to contain the relevant JIRA issues. As Sasha (Software Developer), I would like to commit changes to non-protected branches (work/dev branches) without any restriction.
Intended users
User experience goal
The user should be able to push any commit messages to non-protected branches. The user should not be able to push non-compliant commit messages to protected branches.
Proposal
Limit the commit messages restriction to specific branches, either by name or by type (protected/not protected branches).
What is the type of buyer?
This should be at least Starter tier, as the whole push restrictions are at this tier. This might as well be locked to Premium users.