Use the integrated Git client

Use the integrated Git client to inspect and manage a local Git repository without leaving Kora. It works with repositories in local project folders. SSH and agent folders are not supported; a Git remote is GitHub, GitLab, or another remote configured for a local repository.

Open the Git client

1. Open the Explorer sidebar.
2. Expand Git.
3. The summary shows the current branch, working-tree status, and recent history.
4. Select Open Git workspace to open the full Git view in the main area.

The full Git view contains Changes, History, Branches, and Sync.

Changes: stage and commit work

Changes separates files into these groups:

Group	Files shown
Staged	Files included in the next commit.
Changes	Modified files that are not staged.
Untracked	New files not yet added to Git.
Conflicted	Files with Git conflicts to resolve.

Stage files

1. Find a modified or untracked file.
2. Select Stage.

Use Stage all to include every change. Use Unstage for one file or Unstage all to remove every file from the staging area.

Discard a local change

For a file under Changes, use the delete action. Kora asks for confirmation: the panel cannot recover the discarded change.

Create a commit

1. Stage the files to include.
2. Enter a message in Commit message.
3. Enable Amend previous commit only to update the latest commit.
4. Select Commit.

The commit uses the available local Git configuration, hooks, and GPG signature.

History: inspect commits

History displays a commit graph with hashes, messages, branches, and their relationships. Select a commit to open its details and the files it includes.

Branches: create, switch, and delete

Create a branch

1. Open Branches.
2. Enter a name in New branch.
3. Select Create.

The new branch is created and selected automatically.

Switch branch

Find the target branch and select Switch. Git can prevent the switch when incompatible local changes are present.

Delete a branch

1. Choose a branch other than the current branch.
2. Select the delete icon.
3. Confirm the action.

Deletion is safe: Git removes the branch only when it is already integrated.

Sync: fetch, pull, and push

Sync shows:

• ahead: local commits not sent to the remote;
• behind: remote commits not yet available locally.

Fetch

Select Fetch to update information from the remote without changing the current branch.

Pull

• Pull integrates remote changes with a merge.
• Pull rebase integrates remote changes with a rebase.

For safety, pull and push are unavailable when the working tree has changes, untracked files, or conflicts. Commit, stash, resolve, or discard the work first.

Push and force-with-lease

Use Push to send local commits to the configured remote branch.

Force with lease always requires confirmation. Use it only when deliberately rewriting remote history: Git rejects the operation if the remote changed unexpectedly.

Stash, merge, and rebase

In Branches, under Repository tools:

• Stash temporarily saves local changes.
• Apply stash@{N} applies an existing stash.
• Continue rebase resumes a rebase after resolving conflicts and staging the files.
• Abort operation cancels an ongoing merge or rebase and requires confirmation.

To resolve a conflict, edit the files, stage them, then continue the operation. For a rebase, you can also use the terminal:

git add <resolved-file>
git rebase --continue

Current limits

• Only local repositories are supported; SSH and agent folders are out of scope.
• Complex cases remain in the terminal because there is no visual todo-rebase editor.
• Hard reset, remote configuration, hooks, and administrative operations remain in Kora’s integrated terminal.
• Destructive actions exposed by the panel always ask for confirmation.

Daily workflow

1. Open Changes and stage the files.
2. Create a descriptive commit.
3. Open Sync and select Fetch.
4. If you are behind, use Pull or Pull rebase.
5. Select Push.
6. Check History to confirm the result.

Troubleshooting

• “Not a Git repository” → the selected folder does not contain a repository. Open the correct folder, or initialize it in the terminal with git init.
• Push is rejected → select Fetch, run Pull or Pull rebase, resolve any conflicts, then select Push again.