Skip to main content
Connect a Kaneo project to one Gitea repository to sync issues and respond to branch and pull-request activity. You need permission to manage the Kaneo project, a Gitea token that can read the account and repository and write issues, and repository admin access to create its webhook.

​
Connect the repository

  1. Create a personal access token in Gitea under Settings → Applications. Give it the scopes needed to read your user and repository and write issues. The token’s account must also have write access to the target repository.
  2. In Kaneo, open Settings → Projects, select your project, and open Integrations → Gitea.
  3. Enter the Gitea base URL, such as https://git.example.com. Use the final URL directly, without /api/v1, credentials, a query string, or a fragment.
  4. Enter the access token and repository owner and name. You can also browse repositories from the form.
  5. Choose Verify access and resolve any reported problem, then save the connection.
The API must be able to reach your Gitea server. Verification checks the token and repository permissions; it does not prove that webhooks can reach Kaneo in the other direction.

​
Configure the webhook

After saving, Kaneo shows a webhook URL and secret. Copy both into a repository webhook in Gitea under Settings → Webhooks → Add Webhook → Gitea. Select push, pull request, issue, and issue comment events. Include issue label events if your Gitea version exposes that selection. Kaneo handles issue_label; the Git branch/tag Create event is not a label event. The URL has this shape:
Use Gitea’s test delivery, then create a test issue and confirm it appears in Kaneo. A successful test response proves the request arrived; checking the resulting task proves issue sync works. See Gitea’s webhook documentation for its settings and delivery log.

​
Import existing issues

Save the repository connection, verify its current settings, then choose Import Issues. Verification is cleared when you reload the page or change connection details. If import is disabled, verify again. When replacing the token, save it before importing because the importer uses the saved connection.

​
Configure automation

Choose your branch naming pattern in the integration settings. In the project’s Workflow settings, map branch pushes, opened pull requests, and merged pull requests to the intended columns. Try one task first and check its status before adopting the pattern across your team. Every task has a short link built from its workspace and ticket ID, such as https://kaneo.example.com/acme/task/KAN-12/fix-login-timeout. The title at the end is optional and ignored, so https://kaneo.example.com/acme/task/KAN-12 opens the same task. Copy link on a task gives you this link, which shows your workspace’s part of the path. To turn references such as KAN-12 in Gitea commits and pull requests into links, open the repository’s Settings, enable Use External Issue Tracker, and set: The alphanumeric format only matches keys of one to ten uppercase letters. For any other key, choose Regular Expression and match your project’s key exactly, such as (DE_-\d+), (ПРО-\d+), or (OPS\.2-\d+) with the . escaped. To link several projects, list their keys: ((?:KAN|OPS)-\d+).

​
Replace a token or disconnect

To rotate credentials, enter a replacement token, verify access, and save. On an existing connection, an empty token field keeps the saved token; it does not clear it. Choose Disconnect to remove the Kaneo connection. This does not delete the Gitea repository or Kaneo tasks. Remove the webhook in Gitea as well, and revoke its token if nothing else uses it.

​
Troubleshooting