Commit notification comments are added for commits referencing issues in topic branches event when those commits are not intended as final/ready to integrate in main branch.
Add a new hook alter to let any module modify the issues to add a comment on.
User interface changes
New hook alter.
Original report by @drumm
The drupalorg module started using Feature branches, and the comments on commits have gotten quite chatty.
A couple rules I think could help:
- If a commit is on a standard branch name, like
7.x-3.x, keep notifying as we do today. (We can't look for branches being associated with releases, since the commits are still important if the dev release node hasn't been made.
- Otherwise, only comment if the issue's node ID is also in the branch name. This will notify for feature branches that follow the convention of including the ID.
This should keep good notifications for the popular always commit to HEAD workflow. When feature branches are used, we'll notify for commits with both the message and branch name that have the issue ID, and again when merged into a branch for releases.