-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins ver. 2.204.5
GitHub API 1.111
GitHub Branch Source 2.7.1
If multiple, simultaneous PRs are opened for single source branch to different target branches, e.g. a PR to dev and a PR to master, the pr-merge status notification received by GitHub will apply the status notification to all PRs when it should only apply to a single PR.
- relates to
-
JENKINS-55726 GitHub commit status context not unique enough or configurable - jobs always overwrite each other
-
- Open
-
[JENKINS-62924] pr-merge status notification sent to GitHub applies to multiple PRs if source branch has multiple PRs opened to different target branches
Link | New: This issue relates to JENKINS-55726 [ JENKINS-55726 ] |
Assignee | Original: Kirill Merkushev [ lanwen ] |
Comment | [ Right. A simple workaround can be to fail the builds if multiple PRs are detected (which can be queried via GitHub's API). ] |