Use forks from GitTree
A fork is your own copy of a repository on the provider. Create Fork… asks the provider to make one; Add Remote from Fork… adds an existing fork as a remote. Creating a fork changes nothing in your repository until you add it, and an existing remote is never replaced.
Needs GitTree Pro or a running trial; Free keeps every local Git feature. Compare the plans.
On this page
Before you start
- GitTree Pro or a running trial: hosting integrations are part of Pro.
- The repository is cloned and an account is connected for its provider.
Where to find it
- Right-click a remote under Remote in the left panel, or the palette: Create Fork… and Add Remote from Fork….
| Action | macOS | Windows and Linux |
|---|---|---|
| The command palette | ⌘⇧P | Ctrl+Shift+P |
Steps
Create the fork
Choose Create Fork…, pick the Owner and optionally a Name, and press Create Fork. GitTree waits while The provider is copying the repository, then says it is ready.
Add it as a remote
Under Add it as a remote, give the remote a name and press Continue. GitTree says The fork is the remote ….
Push to it by default (optional)
Push to … by Default makes branches without their own push remote push to the fork. Fetching, pulling and what each branch tracks stay as they are.
Expected result
Your fork is a remote: push your branches there and open pull requests back to the original.
Add someone else’s fork
Add Remote from Fork… lists the repository’s Forks. Pick one, choose HTTPS or SSH as its Address, name it and press Add Remote; no credential is ever saved in it.
If something goes wrong
“This account can already push to …”
A fork is optional: you can push branches to the repository directly.
“The provider did not answer. The fork may have been created”
Press Check Again before asking for another fork.
Questions
What if I already have a fork?
GitTree says You already have a fork and offers Use This Fork instead of making another.