GiteaConnection by xpntl
Into xpntlSettings → Connectors → Gitea
01Overview
Every Gitea is self-hosted, so setup starts with one question: can xpntl reach yours? If it can, an access token lets xpntl add each webhook for you. If it is on a private network, xpntl never calls it and you paste one webhook per repository.
02Set it up
Open Settings → Connectors → Gitea, enter your Gitea address, and say whether xpntl can reach it.
In Gitea, open Settings → Applications → Generate New Token. Set repository to Read and Write and user to Read, then paste the token into xpntl. It is stored encrypted.
Turn a repository on and xpntl shows a target URL and a secret, once. In Gitea, open the repository’s Settings → Webhooks → Add Webhook → Gitea, paste both, and trigger on Pull Request.
Put the card’s key, like ABC-12, in the pull request’s title, description or branch. Write it in capitals, as it appears on the card.
03What it does
Gitea’s pull requests are read the same way as GitHub’s: keys in the title, description or branch link the card, and a merge completes it.
WEB-128-rate-limit
In manual mode Gitea reaches out to xpntl. xpntl makes no calls into your network.
Webhooks are added by hand in Gitea.
An admin turns it on in Settings → General. Drafts wait until they are marked ready. Cards already in Review, Done or Canceled are left alone, and each move shows in the card’s activity.
A choice each workspace makes.
The coordination layer for humans + AI. Free SSO on every plan, no per-seat SSO tax.