Interesting suggestion. What is the reason for this needing to be configured on a specific branch level (versus for the whole repo)? Looking forward to your response.
We have several developers working on same project. We fix bugs by pushing to feature branches with commit messages like 'fix bug #89'.
At that time, issues get resolved. Yet, the project isn't deployed until we merge those feature branches to release branches. Our QAs will watch on issue tracker for bug fixing. They always find issues marked as 'resolved' but not really fixed in the application and complain about it.
So we want issues to be resolved after they are merged to release branches (i.e. get deployed).
Thanks - makes sense! We don't have a plan to implement this right now, but we'll leave this issue open to gauge interest.
Given the low interest in this feature since it was raised, and since the team is currently focused on higher priority items, I am closing this issue to reflect that we won't be able to address this in the near future.