Remotes

Use the Remotes tab to manage the Git remote connections for a repository. You can attach an existing repository, publish a new repository, rename or remove a remote, configure fetch and push destinations, and choose the default push remote.

Navigate the Remotes tab

To open the Remotes tab, click Git > Remotes. The tab belongs to the repository it was opened from, and opening it again brings that tab forward rather than making a second one.

Every Git tool tab carries a Git tools control beside its title. Use it to move between Git Summary, Remotes, Submodules, Subtrees, Git LFS, Sparse Checkout, Repository Config, and Hooks. The menu marks the tool you are on, and choosing a tool opens it for this repository, or brings its tab forward when it is already open. Each tool is its own tab, so two projects can each have their own.

Remote connections are listed alphabetically. Each row shows the remote name, its primary fetch URL, and any explicit push URLs. When no push URL is listed, Git pushes to the fetch URL.

Attach an existing remote

To connect the project to a repository that already exists:

1. Open the Remotes tab and click Add Existing.
2. Enter the remote name, such as origin or upstream.
3. In Repository source, type a fetch URL, or click Browse… to pick a repository from a connected provider account.
4. Optionally expand Push URLs to add mirror destinations or exclude the fetch destination from pushes.
5. Check the Authentication line beneath the source field. It names the identity Git will use for this remote: a connected account, your SSH configuration, or your system Git credentials. When more than one connected account matches the host, choose the one you mean.
6. Click Add Remote.

Repository source is the same control used by Clone, Submodules and Subtrees, so a repository you pick through a provider account carries that account with it rather than having its identity guessed from the URL later. See Submodules for the full set of Authentication states.

If setup fails after Git creates the remote, Zide attempts to remove the partial remote. When that cleanup also fails, Zide reports that the remote still exists so you can review or remove it before retrying.

Publish a repository

Click Publish to create a new repository with a connected provider and add it as a remote. Publishing is different from Add Existing, which only connects to a repository that already exists.

Edit a remote

Click Edit in a remote row to change its name, fetch URL, or push URLs. Zide applies the edit as one operation and restores the original Git configuration if a later part of the edit fails. Renaming also preserves Zide’s provider-source and account associations for the remote, including repositories shared by Git worktrees.

Multiple fetch URLs

Git allows a remote to have more than one fetch URL. It fetches from the first one, and when no push URLs are configured it pushes to all of them, so both the membership and the order of the list matter.

A remote with one fetch URL shows a single field, unchanged. Click Add another fetch URL to add one. Once a remote has more than one, drag a row by its handle to reorder it. Move up, move down, and remove buttons remain available for keyboard and non-drag interaction. The remote row in the list shows every fetch URL: the first is labeled fetch, and the rest are labeled also.

A remote must keep at least one fetch URL. Save stays disabled while a URL row is empty, and the last remaining row cannot be removed. Duplicate entries are preserved along with their positions.

Zide writes the whole list as one operation and restores the original configuration if any part of it fails. Edits that do not touch fetch URLs, such as renaming the remote or changing its push URLs, resubmit the list unchanged and leave every fetch URL and its position intact.

Choose the default push remote

For a repository with more than one remote, select the radio control in the Default push column to set remote.pushDefault. With the keyboard, Tab moves to the selected radio (or the first remote when none is selected); the arrow keys choose another remote, and Space selects the focused remote. Click Clear Default Push to return to branch-upstream fallback behavior.

The selector is disabled when the repository has only one remote because Git already uses that remote without needing a repository-wide default.

Remote actions

In the remote connection row, click the following icons to perform a remote action.

Icon	Description
Prune Branches	Remove stale remote-tracking branches.
Prune Tags	Remove local tags that are not on the remote.
Edit	Edit the remote name, fetch URL, and push URLs.
Remove	Remove the remote connection.

Refresh and recovery

The Remotes tab refreshes when the repository’s Git configuration changes, including changes made in an external terminal. If Zide cannot read the remote configuration, the tab shows Remotes couldn’t be loaded with a Retry button. Add, publish, edit, and remove operations remain unavailable until a retry succeeds, preventing stale or incomplete information from being changed.