fix(ci): mirror every successful production release
Some checks failed
CI and deploy / verify (push) Successful in 2m10s
CI and deploy / publish (push) Has been cancelled
CI and deploy / deploy (push) Has been cancelled
CI and deploy / mirror (push) Has been cancelled

This commit is contained in:
Alex 2026-08-28 01:26:27 +02:00
parent daa85d63a1
commit d0fabf95b4
2 changed files with 4 additions and 4 deletions

View file

@ -201,7 +201,7 @@ jobs:
run: rm -rf .ci run: rm -rf .ci
mirror: mirror:
if: github.event_name == 'push' && github.ref == 'refs/heads/main' && vars.MIRROR_ENABLED == 'true' if: github.event_name == 'push' && github.ref == 'refs/heads/main'
needs: deploy needs: deploy
runs-on: docker runs-on: docker
steps: steps:

View file

@ -24,9 +24,9 @@ Forgejo UI:
- `MIRROR_SSH_KEY`: private half of a write-enabled deploy key for - `MIRROR_SSH_KEY`: private half of a write-enabled deploy key for
`git@github.com:Fi3w0/Nereus.git`. `git@github.com:Fi3w0/Nereus.git`.
After registering that deploy key, set the Forgejo Actions repository variable After registering that deploy key, every successful production deployment
`MIRROR_ENABLED` to `true`. The mirror job stays skipped until both sides pushes `main` to GitHub automatically. An absent or invalid mirror credential
are configured, so an absent GitHub credential cannot break production deploys. fails only the final mirror job, after production has already deployed.
Before the first sealed deployment, a cluster administrator must bootstrap the Before the first sealed deployment, a cluster administrator must bootstrap the
deployer's namespaced SealedSecret permission: deployer's namespaced SealedSecret permission: