chore: remove route-issue-shared.yml, no longer used - #113
Merged
Merged
Conversation
It never fit the human-agent Queue -> Propose -> Human review -> Accepted loop this repo builds for (no proposal, no review step, no agent judgment), and its only consumer, dupmachine/ground-control, has now vendored the logic locally instead of depending on it. Closes #110. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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.
Summary
.github/workflows/route-issue-shared.ymland its composite actionactions/route-issue/(action.yml + route_issue.py): a generic, stateless label-based issue transfer with no proposal/review step, which never fit StarCast'sQueue -> Propose -> Human review -> Acceptedloopdupmachine/ground-control, has vendored the logic locally and no longer depends on itproposal-shared.ymlthat referenced it as a pinned-tag example, and adds a CHANGELOGRemovedentry noting this is breaking for any other pinned consumerCloses #110.
Test plan
pre-commithooks (yamllint, pymarkdown, actionlint) pass on the commitroute-issue/route_issueoutside the historical CHANGELOG entry documenting its original addition