Details
-
Suggestion
-
Resolution: Won't Fix
Description
Problem definition
In a Pull Request, the source (S) and destination (D) branch are visible for the PR reviewer.
However, certain commits in branch S may be a merge from another branch (A) into branch S.
The PR reviewer may not want code from branch A to be merged to branch D, but the only way for him/her to find out, is to view each commit seperately.
This information (the branch of each commit in S) is not available in the Pull Requests >> Commits list.
Example for a Mercurial Repository
We have a Pull Request from branch featureA to branch default
Commits 659dd70 and 9454ff8 originally belonged to branch test_fix, not featureA. However, there is no way for the reviewer to know that by viewing the Commits list, they will have to view each commit, one by one
Suggested Solution
In a Pull Request >> Commits list, add a Column 'Branch/es' that shows which branch each commit belongs to.