Fork a repository with repo fork #41

Closed
opened 2026-10-22 22:13:19 -05:00 by jeff · 0 comments
Owner

Part of #36

zfj repo fork [<owner>/<repo>] [--org <org>] [--name <name>] [--remote | --clone] [--protocol ssh|https]

  • The repository: positional, or the clone's remote when none is given (createFork).
  • A fork that already exists (409) is not a failure. Say so, and carry on with --remote or --clone using the existing fork, so running fork --clone twice works.
  • By default the local clone is left alone.
  • --remote, inside a clone of the parent: renames origin to upstream and adds the fork as origin.
  • --clone clones the fork as zfj repo clone does, upstream remote and all.
Part of #36 `zfj repo fork [<owner>/<repo>] [--org <org>] [--name <name>] [--remote | --clone] [--protocol ssh|https]` - **The repository:** positional, or the clone's remote when none is given (`createFork`). - **A fork that already exists** (409) is not a failure. Say so, and carry on with `--remote` or `--clone` using the existing fork, so running `fork --clone` twice works. - **By default the local clone is left alone.** - **`--remote`, inside a clone of the parent:** renames `origin` to `upstream` and adds the fork as `origin`. - **`--clone`** clones the fork as `zfj repo clone` does, `upstream` remote and all.
jeff closed this issue 2026-10-22 23:35:07 -05:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
jeff/zfj#41
No description provided.