PullPlane supports a self-hosted Forgejo code-host path for teams that want agent work to land in the same branch and pull-request flow as the rest of their repository changes.
Current setup path
A workspace owner enters the Forgejo instance URL and a personal access token. The current interface asks for read:user and write:repository scopes, or an all-scope token, and verifies the connection before showing repositories the token can reach.
Unlike the GitHub App flow, there is no per-repository app installation step. Repository access follows the permissions of the connected token.
Branch and pull-request delivery
Projects can select a reachable Forgejo repository. Coding runs clone it into an isolated sandbox, work on the card branch, push changes through the Forgejo connection, and open a pull request for human review.
Credential and merge boundaries
The workspace manages the personal access token's lifecycle, including rotation and revocation. Give it only the repository access the workflow needs. PullPlane keeps merge as a separate human-approved action, while Forgejo remains authoritative for repository state and merge constraints.