Document Forgejo Actions secrets #102

Merged
eblume merged 1 commit from doc/forgejo-actions-secrets into main 2026-02-04 07:32:33 -08:00
Owner

Summary

  • Add "Forgejo Actions Secrets" section to forgejo reference card
  • Document that ARGOCD_AUTH_TOKEN is used by build-blumeops.yaml workflow
  • Note that secrets are stored in 1Password but manually copied to Forgejo (no auto-sync)
  • Add missing build-blumeops.yaml to workflows list
  • Clarify distinction between server config secrets (1Password → Ansible) vs CI/CD secrets (Forgejo UI)

Context

The forgejo-runner ArgoCD app was showing OutOfSync because a previous attempt stored argocd_token in the ExternalSecret. This was incorrect - the token is actually a Forgejo Actions secret, not a k8s secret. Synced the app to remove the drift and added documentation to prevent future confusion.

🤖 Generated with Claude Code

## Summary - Add "Forgejo Actions Secrets" section to forgejo reference card - Document that `ARGOCD_AUTH_TOKEN` is used by `build-blumeops.yaml` workflow - Note that secrets are stored in 1Password but manually copied to Forgejo (no auto-sync) - Add missing `build-blumeops.yaml` to workflows list - Clarify distinction between server config secrets (1Password → Ansible) vs CI/CD secrets (Forgejo UI) ## Context The forgejo-runner ArgoCD app was showing OutOfSync because a previous attempt stored `argocd_token` in the ExternalSecret. This was incorrect - the token is actually a Forgejo Actions secret, not a k8s secret. Synced the app to remove the drift and added documentation to prevent future confusion. 🤖 Generated with [Claude Code](https://claude.ai/code)
- Add Forgejo Actions Secrets section for repo-level CI/CD secrets
- Note that secrets are also in 1Password but manually synced
- Add missing build-blumeops.yaml workflow to list
- Clarify distinction between server config secrets vs CI/CD secrets

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
eblume merged commit aabfcf6fc0 into main 2026-02-04 07:32:33 -08:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
eblume/blumeops!102
No description provided.