Forgejo and Gitea

Splitkick works with any git remote: Forgejo, Gitea, GitLab, a bare repository over SSH, or a self-hosted server. Worktrees, diffs, review, commits and push are plain git and do not care where the remote lives.

Issues and pull requests

There is no built-in Forgejo or Gitea dashboard yet (it is on the roadmap). Today the agents do it with the forge's own CLI, which you install and sign in to once:

• Forgejo: fj or the API.
• Gitea: tea or the API.

Then, in a session: "Open a pull request for this branch with tea", or "List the open issues with fj and pick the oldest." The agent runs the CLI in the worktree with your login; Splitkick does not see the credentials.

Tips

• Keep the forge CLI configured for the remote's host (tea login add, fj auth login) before you ask an agent to use it, so the agent is not the one typing your token.
• Push from Splitkick, then let the agent open the PR, or let the agent do both.