Inventory of every ACT rule: one generated GitHub issue per rule, shown in a
table Project. A weekly Action (and manual dispatch) recomputes status from
act-rules.github.io and w3c/wcag-act-rules using
act-tools.
Issue titles and bodies are generated by the bot. Do not edit the body. Leave comments instead.
Community Group issues on act-rules/act-rules.github.io with the Blocker
label become cross-repo sub-issues of the matching act-board rule (or the
lowest rule id, when one blocker matches several rules). Removing that label
or closing the CG issue is how a blocker falls off the board.
Create these on the repository before the first workflow run. The job fails immediately if they are missing.
Actions secrets
APP_ID— GitHub App id foract-board-sync(or the org app installed on this repo andact-rules.github.io)APP_PRIVATE_KEY— App private key (PEM). Never commit this value.
Actions variables
ACT_BOARD_PROJECT_NUMBER— Projects v2 number for the ACT board table
The App needs Contents and Issues read/write on act-board and
act-rules.github.io, Metadata read, and organization Projects read/write.
.github/workflows/sync.yml runs Mondays at
06:00 UTC and on workflow_dispatch. It:
- Classifies every rule (
yarn approval-report) - Upserts act-board issues and blocker sub-issues
- Syncs Project Status and optional fields (type, counts, dates, review PR URL) when they differ from the classifier
- Commits
data/snapshot.jsononly when that JSON actually changed
Optional Project fields that do not exist yet are skipped with a warning. A missing Status field fails the job.
Manual run: Actions → Sync ACT board → Run workflow.
The workflow checks out act-tools at
0e5820e
(the act-tools#71 merge on
main). Bump that ref when the board job should pick up newer act-tools.
GitHub disables scheduled workflows in repositories with no activity for 60 days, and emails the repository admins when it does. If the weekly run stops, push a commit or re-enable the workflow from the Actions tab.