change to GH token
All checks were successful
Renovate / Run Renovate (push) Successful in 8s

This commit is contained in:
2025-11-06 13:32:26 +07:00
parent d86315bca6
commit 098da8a988
2 changed files with 16 additions and 4 deletions

View File

@@ -44,10 +44,21 @@ Documentation for the renovate-config repository explaining setup and usage.
- Edit `config.js` to match your Gitea endpoint
- Edit `autodiscoverFilter` to match your organization/user
- Add `RENOVATE_TOKEN` as repository secret
- Optionally add `GITHUB_TOKEN` for GitHub releases
- Optionally add `GH_TOKEN` for GitHub releases (not `GITHUB_TOKEN` - see Gitea naming rules below)
### Gitea Secret Naming Rules
Gitea has specific rules for secret names:
- Must contain only alphanumeric characters ([a-z], [A-Z], [0-9]) or underscores (_)
- Cannot start with `GITHUB_` or `GITEA_` prefix
- Cannot start with a number
- Not case-sensitive
- Must be unique at the repository level
**Therefore**: Use `GH_TOKEN` instead of `GITHUB_TOKEN` for the GitHub access token.
## See Full Documentation
For complete setup instructions, see:
- [RENOVATE.md](../RENOVATE.md) - Full Renovate documentation
- [Official Gitea Tutorial](https://about.gitea.com/resources/tutorials/use-gitea-and-renovate-bot-to-automatically-monitor-software-packages)
- [Official Gitea Tutorial](https://about.gitea.com/resources/tutorials/use-gitea-and-renovate-bot-to-automatically-monitor-software-packages)