docs(launchpad): document gh repo set-default for this fork - #172
Merged
Conversation
In a fresh clone with no default set, gh resolves issue/PR operations to block/buzz (the parent repository) rather than this fork for any command with no explicit --repo — measured: gh issue view 116 failed to resolve an issue that exists here, and gh pr ready 124 reported block#124, a different closed PR (#136). The dangerous case is a write that succeeds silently: gh issue create and gh pr comment resolve through the same base-repository path, so an agent that builds a command programmatically and omits --repo posts into upstream's public tracker with no warning at all. Documented the one-time fix (gh repo set-default launchpad-26/buzz) in both places the issue named: launchpad/README.md's "Opening a PR" section, and launchpad/AGENTS.md §6 alongside the gh pr create examples that assume it. launchpad/scripts/test-gh-set-default-guidance.sh confirms both files mention the command; confirmed it fails against the pre-fix files. Verified: $ bash launchpad/scripts/test-gh-set-default-guidance.sh 2 passed, 0 failed Closes #136 Signed-off-by: Serina Mcfall <serina.mcfall@gmail.com>
serina-mcfall
marked this pull request as ready for review
August 14, 2026 22:03
This was referenced Aug 16, 2026
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
2 participants
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
A fresh clone with no default
ghrepo set resolves issue/PR operations toblock/buzz(the parent) rather than this fork for any command missing--repo— measured,gh issue view 116failed andgh pr ready 124reported the wrong repo's PR. Documented the one-time fix (gh repo set-default launchpad-26/buzz) in both places the issue named.Related issue
Closes #136
Issue type
Bug
Agent provenance
Objective
Tell contributors, in the setup-adjacent sections the issue identified, to run
gh repo set-default launchpad-26/buzzonce per clone.Impacted components
launchpad/README.md("Opening a PR" section)launchpad/AGENTS.md(§6, alongside thegh pr createexamples)launchpad/scripts/test-gh-set-default-guidance.sh(new)Approach and rejected alternatives
Documentation only, placed exactly where the issue's own "Impacted components" section named. No alternative considered — the issue's fix is "add one command to the setup instructions," not a design choice with competing approaches.
Verification
Command run:
Raw output:
Confirmed this fails against the pre-fix files:
Not verified
ghbase-repository assumption — the issue's own "Not verified" section already named this as unchecked, and it's out of scope for a docs fix addressing the setup instructions specifically.git worktree(the issue's own body describes it — landing in shared.git/configunlessextensions.worktreeConfigis set — but I did not independently re-measure it).Security implications
None. Documentation only.
Escalations
None.