v0.6.1: add -R/--repo flag to prs, issues, checks#7
Merged
Conversation
Without -R, every gh subcall in prs/issues/checks defaulted to the
agent's cwd for repo resolution. When the Discord agent was asked
about a PR in a different repo than the one it was running from,
gh either pointed at the wrong repo or 404'd. The user saw the
agent loop on the same `prs view 5 --comments` call 8+ times trying
to surface a PR that DID exist — just not in the merlin tree gh
was sitting on.
Add a uniform -R, --repo OWNER/NAME flag across:
- prs (all actions: list, view, create, comment, review, merge,
close, reopen)
- issues (all actions: list, view, create, comment, close, reopen)
- checks (with a sensible default-branch fallback when -R is given
but --branch isn't)
repo already had it via 0.6.0. Plugin description + arg description
in plugin.toml updated to surface -R prominently so the agent picks
it on the first attempt.
Bash strict-mode safe (REPO_FLAGS uses the +-form expansion);
shellcheck clean.
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
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
1 participant
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
Closes the cross-repo gap in v0.6.0. Without
-R, everyghsubcall inprs/issues/checksdefaulted to the agent's cwd for repo resolution. When a Discord-driven agent (running in one project's worktree) was asked about a PR in a different repo, it either pointed at the wrong repo or 404'd. We saw the corvidagent loop onprs view 5 --comments8+ times trying to surface a PR that did exist — just not in the merlin tree gh happened to be sitting on.Changes
Uniform
-R, --repo OWNER/NAMEacross:prs— list, view, create, comment, review, merge, close, reopenissues— list, view, create, comment, close, reopenchecks— with a default-branch fallback when-Ris given but--branchisn'trepoalready had it via #6. Plugin and arg descriptions inplugin.tomlupdated to surface-Rprominently so the agent picks it up on the first attempt.Test plan
bash -nclean acrossbin/shellcheck --severity=warningcleanprs view 5 -R CorvidLabs/corvid-verify --jsonreturns the right PR from outside that repo's treeissues list -R CorvidLabs/merlin --limit 3works from any cwd