Overview
The Gitea integration links a Kaneo project to a repository on your Gitea instance. Tasks sync with issues, and webhooks keep Kaneo updated when issues, pull requests, or pushes change. You need:- Gitea base URL: e.g.
https://git.example.com. - Personal access token with permission to read/write issues and repository contents for the target repo.
- Repository owner and name: same as in the Gitea UI.
Personal access token
- In Gitea, open Settings → Applications → Generate New Token (paths may vary slightly by version).
- Enable scopes for repository and issues (write access where needed).
- Copy the token and store it securely; paste it into Kaneo’s Gitea integration settings.
Webhook in Gitea
Kaneo verifies incoming webhooks with a HMAC SHA256 secret stored per integration.Where to create the webhook in Gitea
- Log in to Gitea and open the same repository you linked in Kaneo (
owner/repo). - Open the repository Settings.
- In the left sidebar, open Webhooks (sometimes grouped under a “Repository” section).
- If you do not see it, you need admin access to that repository (owner or collaborator with admin).
- Click Add Webhook and choose Gitea.
https://<your-gitea-host>/<owner>/<repo>/settings/hooks
Example: https://git.example.com/acme/my-app/settings/hooks
Configure the webhook
- Connect the repository in Kaneo Project → Integrations → Gitea and save.
- Copy the Webhook URL and Secret shown in Kaneo (after saving).
- In Gitea: Add Webhook → Gitea.
- Set Payload URL to the Kaneo webhook URL.
- Set Secret to the exact value from Kaneo.
-
Enable Content type:
application/json. -
Enable events:
- Push
- Pull requests
- Issues (open, close, label, edit, etc.)
- Issue comments
- Create (used for label creation events on some Gitea versions)
-
Save and use Test Delivery to confirm a
200response from Kaneo.
https://your-kaneo-host/api/gitea-integration/webhook/<integrationId>