Implement sync of GitHub pull request reviewers and Collaborator reviewers
Submitted on behalf of Debdas Mondal (HSBC). GitHub pull requests may have reviewers assigned to them. It should be possible to synchronize the list of pull request reviewers and the list of a linked Collaborator review's participants.
Tracked Branch regex/globbing for Remote Repository Integration
When configuring GitHub or GitLab in Remote System Integration, a branch(es) to track must be entered if "master" isn't the only branch you want to track. This controls which branches targeted for a merge as part of a pull/merge request will automatically create Collaborator reviews. In a pretty common git workflow, release branches are created for use as hardening/stable branches in addition to the mainline branch. If automatic Collaborator reviews based on pull/merge requests against these release/stability branches are also desired, they have to be included in the Remote System Integration list for the repo they're in. In our use case, we create a branch "rel_v##.##" for our hardening and release candidates as we're getting close to release. This branch is named and numbered related to the specific release number. That means we currently need to modify the Remote System Integration for our repositories every time we approach release. If glob or regex patterns could be specified for the Remote System Integration branches to track (at least for GitHub and GitLab), it would resolve the problem of constantly having to modify the Remote System Integration setting for a number or repos. As long as a consistent naming convention was used for branches, those branches that should be tracked could be specified once as a pattern and then never need to be updated again.GitHub/GitLab Integration: Selectable default template by project
When a Collaborator review is created from a pull/merge request through the GitHub/GitLab remote integration, it would be nice if a template could be configured to be automatically selected based on the project the pull/merge request came from. Different projects may have different workflows, so setting a default template for the Collaborator review based on the project would set the proper workflow. Currently the default template is the last one the user creating the review (which is matched from the user creating the pull/merge request) used.
