MIL-002 (tasks 2-7) and the acceptance of MIL-002 to MIL-004.
Marks MIL-002, MIL-003 and MIL-004 as Accepted in their version histories (first commit).
Sync workflow: failures are reported as ERROR: [category] message (configuration, credentials, permissions, api). Before changing anything, the workflow checks that the GitHub token can administer the mirror repository and stops with a permissions error otherwise. No secret value is printed.
Adds guides/onboarding.md (steps, runner labels and prerequisites), guides/credentials.md (minimum permissions, preflight, rotation) and guides/troubleshooting.md (every message mapped to a category and a fix).
Adds 12 offline tests (58 in total, run in a venv) and updates the README capability table.
Records the scoped workflow check in MIL-002: Gitea 1.27.3 runs the workflow in this repository (run 16).
Notes for the reviewer
Behaviour change: error text and category prefixes changed; the preflight adds one extra GitHub GET before the update.
Not verified: delivery of the scoped workflow to other repositories, and the minimum token permissions (taken from documentation; S05 should confirm with minimal tokens).
Not done: MIL-002 task 1 (brief use cases) needs a use case diagram and user stories first. Issue #8 stays open.
No RC-* review records exist for the accepted milestones.
No issue closed: every MIL-002 task issue stays open for review.
## Summary
MIL-002 (tasks 2-7) and the acceptance of MIL-002 to MIL-004.
- Marks MIL-002, MIL-003 and MIL-004 as `Accepted` in their version histories (first commit).
- Sync workflow: failures are reported as `ERROR: [category] message` (`configuration`, `credentials`, `permissions`, `api`). Before changing anything, the workflow checks that the GitHub token can administer the mirror repository and stops with a `permissions` error otherwise. No secret value is printed.
- Adds `guides/onboarding.md` (steps, runner labels and prerequisites), `guides/credentials.md` (minimum permissions, preflight, rotation) and `guides/troubleshooting.md` (every message mapped to a category and a fix).
- Adds 12 offline tests (58 in total, run in a venv) and updates the README capability table.
- Records the scoped workflow check in MIL-002: Gitea 1.27.3 runs the workflow in this repository (run 16).
## Notes for the reviewer
- Behaviour change: error text and category prefixes changed; the preflight adds one extra GitHub `GET` before the update.
- Not verified: delivery of the scoped workflow to other repositories, and the minimum token permissions (taken from documentation; S05 should confirm with minimal tokens).
- Not done: MIL-002 task 1 (brief use cases) needs a use case diagram and user stories first. Issue #8 stays open.
- No `RC-*` review records exist for the accepted milestones.
No issue closed: every MIL-002 task issue stays open for review.
Refs #9
Refs #10
Refs #11
Refs #12
Refs #13
Refs #14
Refs #8
Set the owner/reviewer revision of each milestone to Accepted and deprecate
its initial row, as the Product Owner accepted the milestones. No task
content changed.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Sync workflow: every failure is now reported as `ERROR: [category] message`
with the categories configuration, credentials (HTTP 401), permissions
(HTTP 403) and api (other HTTP errors, unreachable service); HTTP 404 is a
configuration error. Before changing anything the workflow checks that the
GitHub token can administer the mirror repository and stops with a
permissions error otherwise. No secret value is printed.
Guides: onboarding (with runner labels, prerequisites and offline runner
symptoms), credentials (minimum permissions, preflight, rotation) and
troubleshooting (every message mapped to a category and a fix). README
capability table updated. MIL-002 records the verification of scoped
workflow support: Gitea 1.27.3 runs the workflow in this repository;
delivery to other repositories is not yet verified.
Task: MIL-002#2
Task: MIL-002#3
Task: MIL-002#4
Task: MIL-002#5
Task: MIL-002#6
Task: MIL-002#7
Refs #9
Refs #10
Refs #11
Refs #12
Refs #13
Refs #14
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
MIL-002 (tasks 2-7) and the acceptance of MIL-002 to MIL-004.
Acceptedin their version histories (first commit).ERROR: [category] message(configuration,credentials,permissions,api). Before changing anything, the workflow checks that the GitHub token can administer the mirror repository and stops with apermissionserror otherwise. No secret value is printed.guides/onboarding.md(steps, runner labels and prerequisites),guides/credentials.md(minimum permissions, preflight, rotation) andguides/troubleshooting.md(every message mapped to a category and a fix).Notes for the reviewer
GETbefore the update.RC-*review records exist for the accepted milestones.No issue closed: every MIL-002 task issue stays open for review.
Refs #9
Refs #10
Refs #11
Refs #12
Refs #13
Refs #14
Refs #8