Repository navigation
refactor(skills): drop the scope listing from issue-operations - #152
Merged
Merged
Conversation
Only forge-batch listed Issues by milestone, label or epic. Move the two single-Issue queries that survive it to where they are used: an Issue's dependency references into open-work's Prerequisites, and an epic's open sub-issues into Read Issue.
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.
Only
forge-batchlisted Issues by milestone, label or epic, and it was removed in #151, so List Issues by Scope had no caller left.Notes
open-work.mdpointed at that section'sdepsfilter for an Issue's prerequisites. The same filter now sits in Prerequisites as a single-Issuegh issue view --json body,blockedBycall.forge-implementreads an Issue's sub-issues.modecapture, which nothing else read.issue-operations.mdgoes from 655 to 527 words.Exercised
gh issue view 141 --json body,blockedBy --jq '<deps filter>', copied fromopen-work.md→[], exit 0 (gh 2.103.3)gh issue view 141 --json subIssues,body --jq '<sub-issue filter>', copied fromissue-operations.md→[], exit 0scripts/check-skills.sh→ no output, exit 0forge-implementrun on an Issue with a real blocker or sub-issues; Issue 141 has neither, so the filters ran but matched nothinggh issue view <an Issue with "Blocked by #N" in its body> --json body,blockedBy --jq '<the filter in open-work.md>'should print[N]