Source control and pull requests

Tallpine watches GitHub pull requests and GitLab merge requests associated with active sessions. It shows their state, checks, mergeability, and reviews in lifecycle and desktop views. Some review and check details differ by provider.

The provider tracks:

pull request identity and state;
check status and failing check names;
mergeability and merge-conflict reasons;
review decisions and unresolved human-review comment counts.

For GitHub, authenticate gh. For GitLab, the daemon resolves TALLPINE_GITLAB_TOKEN, then GITLAB_TOKEN, then authenticated glab credentials. Use an account with access to the repository and the actions you intend to perform.

To connect a self-managed GitLab host:

Add its hostname to the daemon's TALLPINE_GITLAB_ALLOWED_HOSTS setting. Include the port if the host uses one; omit https://. GitLab.com is already allowed.
If the host needs a separate token, add a host=token entry to TALLPINE_GITLAB_HOST_TOKENS.
Restart Tallpine so its daemon reads the new settings. If the desktop app manages the daemon, quit completely and reopen Tallpine; on macOS, use Quit Tallpine Completely in the menu-bar tray.

For example, in a shell that launches Tallpine:

export TALLPINE_GITLAB_ALLOWED_HOSTS="gitlab.example.com"
export TALLPINE_GITLAB_HOST_TOKENS="gitlab.example.com=YOUR_GITLAB_TOKEN"

Replace YOUR_GITLAB_TOKEN with the token for that host. These are daemon environment settings, not project settings. Do not put tokens in project JSON or docs. Without a host-specific token, Tallpine uses TALLPINE_GITLAB_TOKEN, then GITLAB_TOKEN, then authenticated glab credentials.

When a numeric PR/MR reference is ambiguous, include its full URL. If the Git remote points to a fork but claims should target the upstream, set the project's canonicalRepoURL. This trusts the upstream for claims without changing where Tallpine checks out or pushes. A claim records ownership; it does not check out the PR/MR branch. Tallpine sends merge actions to the owning provider. GitHub review actions may differ on GitLab.

See GitHub SCM and GitLab for authentication and the current action surface.