Skip to content

fix: create roadmap forks with supported gh flags - #9

Open
eohjelle wants to merge 1 commit into
TauCetiProject:mainfrom
eohjelle:agent/fix-fork-command
Open

fix: create roadmap forks with supported gh flags#9
eohjelle wants to merge 1 commit into
TauCetiProject:mainfrom
eohjelle:agent/fix-fork-command

Conversation

@eohjelle

@eohjelle eohjelle commented Aug 6, 2026

Copy link
Copy Markdown

Summary

  • remove the unsupported --remote=false flag from fork creation
  • assert the exact supported fork command in the outside-contributor regression test

Root cause and impact

push_target() passed a positional repository together with --remote=false. Current GitHub CLI rejects any explicit --remote flag 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/run
  • successfully created the contributor fork with gh repo fork TauCetiProject/TauCetiProgress --clone=false using GitHub CLI 2.96.0

Closes #8

🤖 Prepared with Codex

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fork publication fails with current GitHub CLI

1 participant