docs: use CURSOR_BOT_TOKEN for Gitea secret naming rules
Document Gitea secret name constraints and replace GITEA_TOKEN with CURSOR_BOT_TOKEN in README workflow example and SOUL guidance. Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
@@ -14,7 +14,9 @@ Action Runners must be set up and working on your Gitea instance.
|
|||||||
2. **Log in as the cursor user** and create an API token with repository access. Store it as a secret, then log out.
|
2. **Log in as the cursor user** and create an API token with repository access. Store it as a secret, then log out.
|
||||||
3. **Add the cursor user** as a member to repositories where you want AI assistance.
|
3. **Add the cursor user** as a member to repositories where you want AI assistance.
|
||||||
4. **Add the workflow** below to your repository's `.gitea/workflows/` directory.
|
4. **Add the workflow** below to your repository's `.gitea/workflows/` directory.
|
||||||
5. **Store secrets** `CURSOR_API_KEY` and `GITEA_TOKEN` in the repository (or org) secrets.
|
5. **Store secrets** in the repository (or org). Gitea secret names are case-insensitive, alphanumeric/underscore only, and **must not** start with `GITEA_` or `GITHUB_`:
|
||||||
|
- `CURSOR_API_KEY` — Cursor API key
|
||||||
|
- `CURSOR_BOT_TOKEN` — Gitea API token for the `cursor` bot user
|
||||||
|
|
||||||
## Workflow file
|
## Workflow file
|
||||||
|
|
||||||
@@ -34,7 +36,7 @@ jobs:
|
|||||||
- uses: https://gitea.schwenk.online/froxxxy/cursor-gitea-agent@main
|
- uses: https://gitea.schwenk.online/froxxxy/cursor-gitea-agent@main
|
||||||
with:
|
with:
|
||||||
cursor_api_key: ${{ secrets.CURSOR_API_KEY }}
|
cursor_api_key: ${{ secrets.CURSOR_API_KEY }}
|
||||||
gitea_token: ${{ secrets.GITEA_TOKEN }}
|
gitea_token: ${{ secrets.CURSOR_BOT_TOKEN }}
|
||||||
gitea_base_url: https://gitea.schwenk.online
|
gitea_base_url: https://gitea.schwenk.online
|
||||||
ai_model: composer-2.5
|
ai_model: composer-2.5
|
||||||
```
|
```
|
||||||
|
|||||||
@@ -52,3 +52,4 @@ Fränky and repos on gitea.schwenk.online where the `cursor` bot user is a colla
|
|||||||
- Skip LICENSE and test suite unless explicitly requested.
|
- Skip LICENSE and test suite unless explicitly requested.
|
||||||
- Parse event context from `GITHUB_EVENT_PATH` with `jq` — do not rely on undocumented `gitea.event.*` template fields in shell scripts.
|
- Parse event context from `GITHUB_EVENT_PATH` with `jq` — do not rely on undocumented `gitea.event.*` template fields in shell scripts.
|
||||||
- Install Cursor CLI and gitea-mcp only when `@cursor` fires and only if not already present on the runner.
|
- Install Cursor CLI and gitea-mcp only when `@cursor` fires and only if not already present on the runner.
|
||||||
|
- Gitea secret names cannot start with `GITEA_` or `GITHUB_` — use `CURSOR_BOT_TOKEN` for the bot token, not `GITEA_TOKEN`.
|
||||||
|
|||||||
Reference in New Issue
Block a user