fix: create roadmap forks with supported gh flags - #9
Open
eohjelle wants to merge 1 commit into
Open
Conversation
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
--remote=falseflag from fork creationRoot cause and impact
push_target()passed a positional repository together with--remote=false. Current GitHub CLI rejects any explicit--remoteflag when a repository argument is present, so contributors without canonical roadmap write access failed before their fork was created.The corrected invocation,
gh repo fork <repository> --clone=false, matches the established fork-creation command used by TauCetiWorker for work on TauCeti.Validation
./tests/rungh repo fork TauCetiProject/TauCetiProgress --clone=falseusing GitHub CLI 2.96.0Closes #8
🤖 Prepared with Codex