interactive: restore and fail-close the stale GitHub mirror #826

New issue

Open

opened 2026-07-31 08:14:48 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-07-31 08:14:48 +00:00

Member

Follow-up from #823 post-merge release verification.

Observed on 2026-07-31:

Forgejo main and release are at 47869b6114.
Forgejo created aos-v0.142.0 and aos-precommit-v0.1.0 on that commit.
Main mirror run 2590 passed. A guarded manual mirror dispatch, run 2594, also passed.
The GitHub mirror still cannot resolve commit 47869b6114 or either new tag. Its visible main tree remains older than PR #818.
scripts/ci/mirror-to-github.sh exits successfully when GITHUB_MIRROR_PAT is empty, so a missing repository secret is the leading explanation for green no-op runs. This is an inference from observed state. Do not inspect or post the secret value.

Operator verification needed:

Confirm the Forgejo repository secret GITHUB_MIRROR_PAT exists, targets the current GitHub repository after its ownership move, and retains push permission.
Dispatch mirror-to-github.yml on main and verify GitHub main plus aos-v0.142.0 and aos-precommit-v0.1.0 resolve to 47869b6114.
Make the mirror workflow fail closed, or emit a non-success terminal signal, when its required PAT is absent so a green run proves replication occurred.

Forgejo is canonical. This downstream mirror gap does not invalidate the green main CI, promotion, or Forgejo release for #823.

Follow-up from #823 post-merge release verification. Observed on 2026-07-31: * Forgejo main and release are at 47869b61147d7cb88252e48096f1fff139f5902b. * Forgejo created aos-v0.142.0 and aos-precommit-v0.1.0 on that commit. * Main mirror run 2590 passed. A guarded manual mirror dispatch, run 2594, also passed. * The GitHub mirror still cannot resolve commit 47869b61147d7cb88252e48096f1fff139f5902b or either new tag. Its visible main tree remains older than PR #818. * scripts/ci/mirror-to-github.sh exits successfully when GITHUB_MIRROR_PAT is empty, so a missing repository secret is the leading explanation for green no-op runs. This is an inference from observed state. Do not inspect or post the secret value. Operator verification needed: 1. Confirm the Forgejo repository secret GITHUB_MIRROR_PAT exists, targets the current GitHub repository after its ownership move, and retains push permission. 2. Dispatch mirror-to-github.yml on main and verify GitHub main plus aos-v0.142.0 and aos-precommit-v0.1.0 resolve to 47869b61147d7cb88252e48096f1fff139f5902b. 3. Make the mirror workflow fail closed, or emit a non-success terminal signal, when its required PAT is absent so a green run proves replication occurred. Forgejo is canonical. This downstream mirror gap does not invalidate the green main CI, promotion, or Forgejo release for #823.

coilyco-ops added the

autonomy

live-collab

label

2026-07-31 08:14:48 +00:00

coilyco-ops referenced this issue

2026-07-31 09:31:18 +00:00

Inspect failed dev-base gates and authorize PRs #818 and #821 #823

coilyco-ops added the

priority

label

2026-07-31 09:45:42 +00:00