Repository navigation
Commit 9b019cc
feat(mirror): add mirror.yml — 7 secrets and 2 forges enabled, no workflow to use them (#38)
## What
Adds the standard `mirror.yml` caller. New file, 17 lines, identical in
shape to every other consumer in the estate.
## Why
This repo was configured for mirroring but had no workflow to do it:
| Fact | Value |
|---|---|
| `GITLAB_MIRROR_ENABLED` | `true` |
| `RADICLE_MIRROR_ENABLED` | `true` |
| Mirror deploy-key secrets present | **7 of 7** |
| `.github/workflows/mirror.yml` | **404 — absent** |
So the variables and all seven deploy keys were set and nothing consumed
them. The public face of the estate had no off-GitHub backup at all.
Found by the estate backup audit (390 repos swept, 309 have
`mirror.yml`, 119 have a forge enabled, 97 actually push). This repo was
in the small **enabled-but-no-workflow** class — distinct from the 271
repos with no forge enabled, and distinct from the 18 whose whole
governance suite is startup-dead on a stale pin.
## Not a green no-op
Because all 7 secrets are present and 2 forges are enabled, this
workflow will make real pushes to GitLab and Radicle on the next push to
`main`, rather than running green and backing up nothing.
## Preconditions checked before writing
- **No `actions.lock`** at the repo root or under `.github/` (both 404),
so no lockfile entry is required. A pure reusable caller in a locked
repo needs a bare `'.github/workflows/mirror.yml': []` entry or it
startup-dies with zero jobs; that class does not apply here.
- **`allowed_actions: all`**, so the reusable's third-party steps are
not refused by the caller's Actions policy. The caller's allowlist, not
the reusable's, is what governs.
- **`sha_pinning_required: true`** on this repo — satisfied, the
reusable is pinned by full 40-character SHA.
- **Pin positive-controlled**: `mirror-reusable.yml` exists at
`8f2ee508…` as blob `1ccafb23041e927a0d9cfc950a5678052fb30672`;
`8f2ee508` is current `standards` main and is independently verified at
mirror = 7 jobs.
- **SPDX header on line 1**, per estate policy.
## Verification is post-merge
The workflow triggers on `push: branches: [main]` and
`workflow_dispatch`, not on `pull_request`, so this PR cannot exercise
it. After merge the push fires it; the run should report 7 jobs, with
GitLab and Radicle doing real work and the other 5 forges skipping on
their disabled flags.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_01TCKh98NmUmfvgpuGyJbNu8
Co-authored-by: Claude Opus 5 <noreply@anthropic.com>1 parent 159e578 commit 9b019cc
1 file changed
Lines changed: 16 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
| 1 | + | |
| 2 | + | |
| 3 | + | |
| 4 | + | |
| 5 | + | |
| 6 | + | |
| 7 | + | |
| 8 | + | |
| 9 | + | |
| 10 | + | |
| 11 | + | |
| 12 | + | |
| 13 | + | |
| 14 | + | |
| 15 | + | |
| 16 | + | |
0 commit comments