Fast-forward protected GitHub mirror after attribution rollover #1613

Closed

opened 2026-07-28 20:29:50 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-07-28 20:29:50 +00:00

Owner

Goal

Fast-forward the GitHub main mirror to canonical Forgejo main after the legacy attribution rollover.

Current evidence

Canonical Forgejo main is complete and clean.
GitHub is strictly behind with no GitHub-only commits.
HTTPS and SSH direct pushes are rejected by required status checks.
The connected GitHub App cannot update refs.
No pull request is authorized for this rollover.
Agent-created staging branches were deleted.

Required operator decision

Temporarily grant a direct-push or ref-update bypass for this repository, then fast-forward GitHub main from canonical Forgejo main and restore the rule immediately.

Done condition

GitHub main and Forgejo main resolve to the same commit.
No temporary branch remains.
No force-push or history rewrite occurs.

Goal Fast-forward the GitHub main mirror to canonical Forgejo main after the legacy attribution rollover. Current evidence * Canonical Forgejo main is complete and clean. * GitHub is strictly behind with no GitHub-only commits. * HTTPS and SSH direct pushes are rejected by required status checks. * The connected GitHub App cannot update refs. * No pull request is authorized for this rollover. * Agent-created staging branches were deleted. Required operator decision Temporarily grant a direct-push or ref-update bypass for this repository, then fast-forward GitHub main from canonical Forgejo main and restore the rule immediately. Done condition * GitHub main and Forgejo main resolve to the same commit. * No temporary branch remains. * No force-push or history rewrite occurs.

coilyco-ops added the

autonomy

live-collab

label

2026-07-28 20:29:51 +00:00

coilyco-ops commented

2026-07-28 20:50:35 +00:00

Author

Owner

Resolved 2026-07-28. GitHub main was fast-forwarded without force from canonical Forgejo main and now matches 8a18fec883. The fleet status-check removal is temporary under infrastructure#670, and required GitHub checks will return after the direct mirror repair window.

Resolved 2026-07-28. GitHub main was fast-forwarded without force from canonical Forgejo main and now matches 8a18fec8832e957be8451ee3a5378a27512b4153. The fleet status-check removal is temporary under infrastructure#670, and required GitHub checks will return after the direct mirror repair window.

coilyco-ops closed this issue

2026-07-28 20:50:44 +00:00

Commenting is not possible because the repository is archived.

No milestone

No project

No assignees

1 participant

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

coilyco-flight-deck/ward#1613

No description provided.

Rows
Columns