ci: Prefer RELEASE_TOKEN over reserved GITEA_TOKEN #15
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
blocked
draft
No milestone
No project
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
s1d3sw1ped/jiggablend!15
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "eva/ci-release-token"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Gitea reserves the secret name GITEA_TOKEN, so we cannot set a custom Actions secret with that name. RELEASE_TOKEN is already populated on this repo with the s1d3sw1ped all-access PAT. Workflows now prefer RELEASE_TOKEN and keep the automatic reserved token as fallback.
Reviewers: please sanity-check the YAML expressions only — no product code changes.