chore: document CI secrets rotation to trigger fresh pipeline #237
No reviewers
Labels
No labels
domain:backend
domain:devops
domain:frontend
status:approved
status:in-progress
status:needs-fix
status:qa
type:bug
type:devops
type:feature
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo_admin/pal-e-api!237
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "232-ci-trigger"
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?
Summary
The
forgejo_tokenWoodpecker secret was empty and has been updated. Restarted pipelines cache old (empty) secrets, so we need a real merge-to-main push event to trigger a fresh pipeline that picks up the corrected secret.Changes
.woodpecker.yaml— added# CI secrets verified 2026-03-28comment at top of file to document the secrets rotation and provide a meaningful diff for the merge commitTest Plan
forgejo_tokenis now populated)Review Checklist
Related Notes
pal-e-api— CI pipeline secrets rotation