froxxxy/cursor-gitea-agent
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: use CURSOR_BOT_TOKEN for Gitea secret naming rules

Browse Source 
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:
Frank Schwenk
2026-07-05 15:40:00 +02:00
parent 0c3f1ab86f
commit 893d7bec1e
2 changed files with 5 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
SOUL.md
+1
View File
@@ -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.
- 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.
- Gitea secret names cannot start with `GITEA_` or `GITHUB_` — use `CURSOR_BOT_TOKEN` for the bot token, not `GITEA_TOKEN`.