Repository Config

You can use the Repository Config tab to view and edit this repository’s configuration keys and tools.

The Repository Config tab uses its owning tab as the editing context. In a Project tab, it edits the repository’s Local configuration, which is shared by all of its worktrees. In a child Worktree tab, it edits configuration for that worktree only.

Global Git configuration is not owned by any project, so it is managed in Settings > Git. See Settings.

Navigate the Repository Config tab

To open the Repository Config tab, click Git > Repository Config. 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.

The Repository Config tab displays the configuration keys and values. You can set the merge tool and diff tool from the Repository Config tab.

Search config keys and the Show: Common / All toggle narrow the list. Add Entry sits directly above the list it adds to.

The kebab menu in the tab’s title row holds the escape hatches. Edit Local Config File opens .git/config in Zide and Edit Worktree Config File opens config.worktree in your default text editor when the current worktree has one; both bypass this table and edit the file as text. Open Global Git Settings leaves the project for Settings > Git, which edits your global configuration with this same table.

There is no action for system configuration. It is machine-wide and lives where only an elevated process can write it, so Zide shows its values but does not offer to change them.

Read resolved values

The Resolved Value column shows the value Git currently uses. Browse mode leaves provenance out so the list stays easy to scan. Git still applies its normal scope precedence: a worktree value beats a local one, and a local value beats a global or system value.

Some keys hold several values, and each one gets its own row under a single key. For a list key such as remote.origin.fetch or include.path that is normal and Git uses all of them; for an ordinary key it usually means a line was duplicated, and Git uses the last one. Zide does not guess which kind a key is, so it shows you all of them and lets you decide.

Click Edit to change that key’s values in the current Project or Worktree context. The displayed values are replaced by one editable field per value at that scope. When another scope also defines the key, Other configured values lists those read-only values in precedence order. Plain-language status text explains which value Git uses and what would be used if the edited setting were removed. Values from the active editing scope are not repeated there.

Git reads a worktree-specific file only when extensions.worktreeConfig is enabled for the repository. If it is not enabled, Repository Config in a Worktree tab remains available for browsing, but Add Entry and Edit are disabled. Zide never redirects those actions to the repository’s shared Local configuration and never enables the extension automatically. Use the parent Project tab when you intend to edit shared Local configuration.

Add a configuration key

To add a configuration key, complete the following steps.

1. In the Repository Config tab, click Add Entry.
2. Enter the name and the value of the configuration key.
3. Click Add.

Press Enter in either field to add the entry without reaching for the button. Cancel discards it.

Only one inline editor can be active. Finish a key edit before using Add Entry, or add or cancel the new entry before editing an existing key.

Change or remove a value

Click Edit on a row. It becomes Done, and each displayed value is replaced in place by the corresponding edit field with Save, Cancel, and Delete controls.

Each field saves on its own.

• Change a value and click its Save. Save and Cancel stay disabled until the field differs from what is on disk.
• Cancel restores that one field.
• After the first value exists, add another field with + Add value, type a value, and save it. When the key has no value at the active editing scope yet, the initial blank field creates the first one and + Add value stays hidden until it is saved.
• Remove a value with Delete, or by clearing its field and saving. Removing asks you to confirm.
• Removing the last value removes the key from the active editing scope.

Done leaves edit mode. It does not save: if a field still holds unsaved text, Zide asks before discarding it.

Two values of the same key that hold identical text cannot be edited separately, because Git identifies a value by its text rather than by its position.

Values from scopes other than the active editing scope are read-only in this editor. Global values are edited in Settings > Git, which uses this same table, and system values remain read-only. When you change a global value there, this table updates to match, so you do not need to reopen it. A global value changed outside Zide, such as by git config --global in a terminal, is picked up the next time this table loads.

New entries are written to Local configuration in a Project tab or Worktree configuration in an enabled Worktree tab.

Edit global configuration

Choose Open Global Git Settings from the kebab menu to open Settings > Git and bring the global configuration table into view. This is one-way navigation: no repository, worktree, or folder context travels with it, and the table shows the same file no matter which project you started from, or whether any project is open.

The two surfaces are the same table with a different editing scope, so searching, filtering, adding, per-value editing, and multiple values all work the same way there. See Settings.