If you set "Discover pull requests from forks" to "Both the current pull request revision and the pull request merged with the current target branch revision" then the build from PR-merge and PR-head would be mixed on the BO PR view.
I like the option of building both the HEAD/MERGE simultaneously.
Its a usability issue if the 'PR-N-head', 'PR-N-merge' can't be distinguished in "Pull Requests" tab.
Fred Vogt
added a comment - This is still a problem as of 2.241 (2020-06-16).
I like the option of building both the HEAD/MERGE simultaneously.
Its a usability issue if the 'PR-N-head', 'PR-N-merge' can't be distinguished in "Pull Requests" tab.
Fred Vogt
added a comment - - edited Added some extra screenshots.
The "Activity" tab of the Pipelines activity view has the "Branch" column.
The "Pull Requests" tab could either add the "-head / -merge" suffix when using:
jenkinsci/github-branch-source-plugin/org/jenkinsci/plugins/github_branch_source/OriginPullRequestDiscoveryTrait.java - BOTH
This is still a problem as of 2.241 (2020-06-16).
I like the option of building both the HEAD/MERGE simultaneously.
Its a usability issue if the 'PR-N-head', 'PR-N-merge' can't be distinguished in "Pull Requests" tab.