What you can do

• Home — personalized feed of repos, open PRs, and issues
• Notifications — inbox for Gitea and Forgejo accounts
• Explore — organizations, teams, webhooks, and labels
• Repos — branches, commits, file tree, PRs, and issues
• Actions — live workflow runs, logs, and artifacts
• Demo — sample server on device, no account (1.18+)

Requirements

• iOS 26+ (iPhone and iPad)
• A Gitea or Forgejo instance or Demo mode
• An API token from your server when not using Demo

In this documentation

Use the sidebar to navigate between sections. Getting Started covers Gitea, Forgejo, Codeberg, and Demo setup. Supporter explains the optional one-time purchase. Deep Links explains how to open GitBoba from links on the web. API Compatibility tracks which Gitea/Forgejo API areas the app currently supports.

The gitboba:// URL scheme

Registered in the app as a custom URL scheme. Tapping a gitboba:// link on iOS opens GitBoba and navigates to the matching screen. The host segment names the resource type; owner, repo, and identifiers follow as path segments.

gitboba://{type}/{owner}/{repo}[/{id}]

Requires GitBoba to be installed. If the app isn't installed, the link won't resolve — use a normal HTTPS link as a fallback for web browsers.

Supported routes

These paths map directly to screens inside the app.

Examples

gitboba://repo/alice/my-repo
gitboba://pull/alice/my-repo/42
gitboba://issue/alice/my-repo/7
gitboba://commit/alice/my-repo/deadbeef
gitboba://notifications

Note the singular hosts: issue and pull, not issues or pulls. Gitea web URLs use the plural form (/issues/42) — those work too when the user has the matching server configured.

Gitea & Forgejo HTTPS URLs

When a user has already added a Gitea or Forgejo server in GitBoba, the app can also open standard web URLs that point at that instance. GitBoba matches the host (and optional subpath prefix) against configured accounts and routes to the right screen.

https://gitea.example.com/alice/my-repo
https://gitea.example.com/alice/my-repo/pulls/146
https://gitea.example.com/alice/my-repo/issues/7
https://gitea.example.com/alice/my-repo/commit/deadbeef

Subpath installations are supported — if the server is at https://git.example.com/gitea, repo URLs include that prefix. When the link targets a different configured account than the one currently active, GitBoba switches accounts automatically.

The open wrapper

For integrations that only have a raw HTTPS link (for example, the iOS share sheet's Open in GitBoba action), wrap the web URL in a gitboba://open link. GitBoba extracts the embedded URL, matches it to a configured account, and navigates accordingly.

gitboba://open?url=https%3A%2F%2Fgitea.example.com%2Falice%2Fmy-repo%2Fissues%2F1

The url query parameter must be a fully URL-encoded HTTPS (or HTTP) link to your Gitea or Forgejo instance. This is the format the share extension uses when handing off from Safari or other apps.

Linking from your site

Add gitboba:// links alongside normal HTTPS links so mobile visitors with GitBoba installed can jump straight into the app. Use the custom scheme when you know owner, repo, and number; use HTTPS when you want the link to work in a browser too.

<!-- Open pull request #42 in GitBoba -->
<a href="gitboba://pull/alice/my-repo/42">Open in GitBoba</a>

<!-- Fallback-friendly: works in browser and in-app when configured -->
<a href="https://gitea.example.com/alice/my-repo/pulls/42">
  View pull request
</a>

To open a deep link on your iPhone or iPad, tap any gitboba:// link in Safari, Mail, or Messages. From a Gitea page in Safari, you can also use Share → Open in GitBoba. In Shortcuts, add an Open URL action with a supported link.

What stays free

Everything your server exposes for normal use through the API — repositories, pull requests, issues, Actions, notifications, file browsing and editing, and merges you could perform in the Gitea or Forgejo web UI. Supporter is never used to withhold standard API parity.

What Supporter adds

• Layout & customization — extra home dashboard styles, tab arrangement, and metrics views, etc.
• GitBoba-only workflows — power features the web apps do not ship, such as merging an entire PR stack in one guided flow (while single-PR merge in a stack remains available without Supporter).

Gitea vs Forgejo

When Gitea and Forgejo differ at the API level, GitBoba shows what your server supports. That is separate from Supporter — missing endpoints on Forgejo (or older Gitea) are not unlocked by purchasing Supporter.

See API Compatibility for coverage details. Purchase handling and privacy are described under In-App Purchase in the privacy policy.