GitHub REST API and gh CLI

Finluth exposes a GitHub Enterprise-style REST v3 endpoint at /api/v3. It supports access tokens created in Git access tokens with GitHub-compatible Bearer and token authorization headers.

The initial compatibility surface covers /user, accessible repositories, branches and labels, issue listing/creation/editing/comments, pull request listing/creation/editing/closing/merging, changed files and commits, reviews, and commit statuses/check runs. Repository permissions and branch rules still apply to writes; issue assignment is limited to one Finluth user with repository access.

Authenticate GitHub CLI

Create a Finluth Git access token, then authenticate against the Finluth host:

printf '%s\n' "$FINLUTH_TOKEN" | gh auth login --hostname git.finluth.com --with-token
gh issue list --repo finluth/finspot
gh pr list --repo finluth/finspot
gh pr view 1 --repo finluth/finspot
gh api repos/finluth/finspot/issues?state=all

Set FINLUTH_TOKEN to a Finluth Git access token before running the login command. Pull request creation expects both branch refs to already exist in the Finluth repository.

REST-oriented gh workflows and scripts can use the host's /api/v3 base. This is a compatibility layer, not full GitHub API parity: GraphQL and unsupported REST endpoints or fields are not implemented, so CLI commands that require them may fail. Use gh api against a supported REST route when a higher-level command depends on an unsupported API.