Merge Rules / Issue Rules
Problem to solve
Separating out the Merges from the Push Rules, in addition, creating a new Issues Rules.
Further details
This would prevent issues where we want to have our team do commits in one format, but once those are done, we don't need to have those same rules apply for Merges, and want the merges to look differently.
In addition, we'd like to be able to make Issues require certain options be set before creation, such as adding at least one label, and input a weight, etc.
Proposal
Have a separate regex option for "Merge Rules" separating it from the push rules. Have a new set of options to define what is required for issues per project or globally.
What does success look like, and how can we measure that?
Adding the above options would allow our team to be more organized and allow pushes to contain one set of required data, whereas merge text would have the option of other criteria. Lastly, having options for issues to require certain options will help to keep issues properly organized.