Roll forward legacy example-bot attribution on seven files #773

New issue

Closed

opened 2026-07-28 19:10:47 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-07-28 19:10:47 +00:00

Owner

Seven tracked files still surface example-bot as their latest author after the three-entity attribution fix landed.

The agent will roll those paths forward with two explicit mode-only commits pushed together. The first commit flips each file mode, and the second restores every original mode. This changes commit history without inventing source or documentation edits.

Acceptance criteria:

All seven paths have a latest commit with the current three-entity attribution.
The final repository tree is byte-for-byte and mode-for-mode identical to the starting tree.
The full pre-commit suite passes.
Forgejo main receives both commits in one push, allowing the normal mirror and release flow to run once.

Seven tracked files still surface example-bot as their latest author after the three-entity attribution fix landed. The agent will roll those paths forward with two explicit mode-only commits pushed together. The first commit flips each file mode, and the second restores every original mode. This changes commit history without inventing source or documentation edits. Acceptance criteria: * All seven paths have a latest commit with the current three-entity attribution. * The final repository tree is byte-for-byte and mode-for-mode identical to the starting tree. * The full pre-commit suite passes. * Forgejo main receives both commits in one push, allowing the normal mirror and release flow to run once.

coilyco-ops referenced this issue from a commit

2026-07-28 19:15:31 +00:00

chore(history): mark legacy attribution rollover, closes #773

coilyco-ops closed this issue

2026-07-28 19:15:31 +00:00

coilyco-ops referenced this issue from a commit

2026-07-28 19:15:31 +00:00

chore(history): complete legacy attribution rollover, closes #773

coilyco-ops referenced this issue

2026-08-29 21:29:31 +00:00

Forgejo action-run logs are unreachable through aosguard, so a red CI job cannot be diagnosed read-only #1426