You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
π Merge queue admits two open PRs claiming one issue when they sit in different lanesΒ #15810
Issue #15773 got two open PRs: the hive's scanner opened #15783 (self lane) and a trusted human opened #15793 (trusted-author lane) for the same issue. The hive detected the pair β both wear conflicts-with-open-pr, the log says "suppressing issue: open external PR covers it", the issue row offers "Let hive decide β all 2 PRs" β but never resolved it: #15793 sat 3rd in the merge queue and #15783 read "Ready for auto merge Β· checking now". Two conflicting implementations of one issue were both marching toward merge.
Root cause
The one-PR-per-issue rule (planDuplicateHolds, #15395) groups only the current lane's candidates by Fixes #N. A hive PR in the self lane and a human PR in the trusted lane never see each other, so neither is held.
Fix (safety gate only β no auto-resolution)
While an issue has two or more open PRs claiming it and no decision has been recorded on a PR, every lane refuses to admit any of them. Lane reason merge-train:claim-conflict#<other>:<issue>, log same-issue claim conflict undecided: #A vs #B.
A recorded operator decision on a PR (Approve and let hive merge, /hive decision approve, β¦) admits that PR; closing the loser (Close as superseded byβ¦) clears the conflict for the other.
Adoption pairs (Supersedes #N) are not conflicts.
Tracker chevron/caption reads "held Β· duplicate of #B Β· needs decision"; the PR parks at 085.
@clubanderson this issue was closed by @hivecommons-hive[bot] as completed.
If this was closed by a merged PR, the fix only takes effect once it ships in a tagged release and your deployment updates to it β check your running version against the fix before concluding the fix failed.
If you are still seeing the problem, comment /reopen and it will be reopened for you β you do not need write access. Please add what you are still observing (running version, logs, steps) so it is not closed the same way again.
Activity
hivecommons-hive commentedon Oct 30, 2026
All children delivered: #15822.
Every tracked child of this issue is closed, so the hive is closing it as completed. Reopen it if something it asked for is still missing.
github-actions commentedon Oct 30, 2026
@clubanderson this issue was closed by @hivecommons-hive[bot] as completed.
If this was closed by a merged PR, the fix only takes effect once it ships in a tagged release and your deployment updates to it β check your running version against the fix before concluding the fix failed.
If you are still seeing the problem, comment
/reopenand it will be reopened for you β you do not need write access. Please add what you are still observing (running version, logs, steps) so it is not closed the same way again.π automerge: hold same-issue PRs across lanes until a decision is recβ¦
π automerge: hold same-issue PRs across lanes until a decision is recβ¦