Repository navigation
feat(graph): follow GitHub sub-issue links - #54
Merged
Merged
Conversation
Parsing of the parent and sub-issue fields, crawling from either end of a link, the hub guard, rank, mentionedBy, the per-node limit and unreadable sub-issues, and how the report, terminal view, cluster prompt and dashboard show the link. A mention between two linked issues keeps its own edge, inbound reference and author. Co-Authored-By: Lars Buur <3585707+LarsBuur@users.noreply.github.com>
An issue attached to an epic only through a GitHub sub-issue link was missing from the graph, because the node query never read the sub-issue fields. The query now reads each issue's parent and its first 50 sub-issues. The parent gets a `parent-of` edge to each readable sub-issue and the sub-issue a `child-of` edge to its parent, so the crawl follows the link from either end under the usual depth, budget and hub rules. These edges sit beside any mention, cross-reference or connection between the same two issues instead of replacing it, so linking two issues keeps the reference in rank and in mentionedBy. The links add no inbound references and never count as closing links. The report labels the edges `parent of` and `child of`, and the dashboard draws one arrow from parent to sub-issue. A parent past the 50 limit records `subIssuesPastLimit`; sub-issues GitHub returns without data are counted in `subIssuesUnreadable`. Co-Authored-By: Lars Buur <3585707+LarsBuur@users.noreply.github.com>
The dashboard model puts sub-issue links in each node's out and in lists, so neighbors() counts them: Impact lists an epic's open sub-issues as follow-ups, and the Swarm links and blast metrics count them, as they already do for Linear parent and sub-issue relations. The docs only said the links add no inbound references. Document the behavior in the graph and dashboard pages and the bundled skill, and pin neighbors, follow-ups and Impact scores in a test. Co-Authored-By: Lars Buur <3585707+LarsBuur@users.noreply.github.com>
A sub-issue link and a mention of the same issue are two edges, so an epic that also lists its sub-issues in a task list counted each one twice and became a hub at half the threshold, leaving its sub-issues unfetched. The hub guard, the hub line in the report, and the component hub in Markdown and the dashboard now count each linked item once. Co-Authored-By: Lars Buur <3585707+LarsBuur@users.noreply.github.com>
The plan treated every edge to a failed or capped-out node as an unresolved reference, so a parent whose sub-issue fell past the node cap, or a sub-issue whose parent failed to fetch, moved to the blocked lane with readiness 0. A sub-issue link is structure, not a reference; only reference edges now block on an unresolved target. Co-Authored-By: Lars Buur <3585707+LarsBuur@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
A new sub-issue link to a node that was already referenced diffed as "no changes" because the previous-edge set held targets only. Key it by `via` and target so a `parent-of` or `child-of` link beside a mention is reported as a new link.
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The crawl reads mentions, cross-references, connected events, and closing references, but not GitHub sub-issue links, so an epic seed does not reach sub-issues it never mentions and a sub-issue seed does not reach its parent or siblings.
Changes
parentand its first 50subIssues; they becomeparent-ofandchild-ofedges beside any mention or cross-reference between the same issues.plan.parent ofandchild of; the dashboard draws one parent-to-child arrow and counts sub-issues as connections in Impact,links, andblast.subIssuesPastLimit, and sub-issues GitHub returns without data are counted insubIssuesUnreadable.Replaces #38.
Visual proof
A synthetic
acme/roadmapepic with two sub-issues that never mention it. Before, the crawl stops at the epic:After, it follows the sub-issue links both ways:
The 32 new tests fail 24 of 32 on base f2fa275 and pass on ff4e8ea.