Documentation

All guidesWorkflow

Git over HTTPS

Clone, review, commit, and push changes with HTTPS remotes and tokens.

4 min read

Use an HTTPS URL

Odete uses libgit2 and works with real repositories per project. When cloning or adding a remote, use the HTTPS URL supplied by GitHub, GitLab, or your own host.

SSH Git is not supported. For a private remote, create a personal access token with the smallest necessary scope and use it to authenticate with the host.

https://github.com/organization/project.git

Review before committing

In the Git pane, inspect Status and the diff. You can stage whole files or hunks, write the message, and create the commit without leaving the project.

Branches, conflict-resolving merges, stash, blame, and file history are part of the flow. An AI-suggested message should still be checked against the staged diff.

  • Inspect the diff.
  • Stage only hunks belonging to the change.
  • Create a local commit.
  • Push to the remote when ready.

Protect credentials

Tokens, Git passwords, and configured accounts live in the iOS Keychain, not in a project file. Removing an account in Settings deletes the stored credentials for that service.

The GitHub pane also uses the GitHub API for pull requests and CI. Device flow needs the app client identifier configured; until then, use a personal token.

Operations outside the scope

Submodules, cherry-pick, and interactive rebase are unavailable. Plan those steps on another machine or adjust the workflow to supported operations.

Fetch, push, clone, pull requests, and CI need a network connection and send credentials and content to the host you chose. Local commits and diffs remain available offline.