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
🐛 Scanner decomposition files child issues in the parent's repo instead of the managed repo where the work lives #18680
When the scanner decomposes a tracker, it files every child issue in the parent's repo, even when the work belongs in another repo the hive manages.
Seen 2026-11-17: the scanner decomposed #18596 at 08:00 and filed #18660 (Windows capture) and #18661 (Linux capture) in hivecommons/hive. All of that code lives in hivecommons/quorum-companion. The scanner knew this; the #18660 body says:
The work lives in hivecommons/quorum-companion; this child keeps the #18596 "Next" checklist actionable. Move or mirror it there if preferred.
The children are linked to the parent with "Part of #18596" and <!-- hive:parent 18596 -->. Both use a bare number, which resolves only within the same repo, so a child in another repo would lose the parent link. As a result:
Closed by #18688 (merged as ef8a7fc). Scanner decomposition now files each child in the managed repo where its work lives, linked to the parent as Part of owner/repo#N with a <!-- hive:parent owner/repo#N --> marker. Tracker progress and the decomposed-parent close count children in any managed repo, and an unmanaged child repo falls back to the parent's repo.
Activity
clubanderson commentedon Nov 17, 2026
Claimed: an operator-dispatched agent is working on this now. Hive agents, please do not pick it up.
hivecommons-hive commentedon Nov 17, 2026
Thanks for filing this issue! To help us reproduce and investigate, could you please include the commit SHA of the build you're running?
You can find it by running:
Or check the bottom of the console UI for the version string.
This issue will be on hold until a SHA is provided. Simply add a comment with the SHA and the label will be automatically removed.
🐛 Cross-repo decomposition children and cross-repo PR issue links
🐛 Cross-repo decomposition children and cross-repo PR issue links
clubanderson commentedon Nov 17, 2026
Closed by #18688 (merged as ef8a7fc). Scanner decomposition now files each child in the managed repo where its work lives, linked to the parent as
Part of owner/repo#Nwith a<!-- hive:parent owner/repo#N -->marker. Tracker progress and the decomposed-parent close count children in any managed repo, and an unmanaged child repo falls back to the parent's repo.🌱 chore: top up v6 from v5 (2026-11-18) (#18929)