fix(ci): restore GitHub issue project sync#9740
Conversation
Project 1 no longer exposes the configured Backlog status, causing every qualifying issue sync to fail before adding the item. Route synced backlog items to the current Someday status while leaving triggers, labels, permissions, and project selection unchanged. Closes BasedHardware#9736.
|
Thanks for the focused CI/workflow repair. I reviewed the actual diff against the linked failure in #9736: this only changes the Project V2 I do not see a code-level blocker in this patch. Because it changes a GitHub Actions workflow that mutates the org project, and because a fork cannot safely exercise the secret-backed live Project V2 mutation, I’m not formally approving it automatically. A maintainer should confirm that by AI on behalf of David — if you need David’s attention urgently, please @Git-on-my-level and escalate with |
What changed and why
Replace the removed
Backlogvalue in the GitHub Issue Sync workflow with the project's current backlog-equivalentSomedaystatus. The action rejects values that are not present in the Project V2 single-select field, so every qualifying issue sync currently fails before adding the item. Closes #9736.Product invariants affected
none
How it was verified
29356714415, which reports thatBacklogdoes not exist and listsSomeday,Next Week,TODO (This week),In progress,In review, andDoneas the available values.Backlogreplaced the original to-do status specifically to route synced issues into the backlog, makingSomedaythe current semantic equivalent.actionlint -shellcheck= .github/workflows/main.yml--base HEADbecause current paths use backslashes while Git base paths use forward slashes; tracked separately in Deployment secret-boundary ratchet treats all bindings as new on Windows #9738.Tests
This is a one-value workflow configuration repair. Static workflow validation and all applicable deterministic checks pass apart from the isolated native Windows path-comparison defect described above. A live Project V2 mutation cannot be exercised from a fork because the upstream project token is intentionally unavailable there.
Root cause and durable guard (bug fixes)
The configured Project V2 status was renamed or removed while the workflow retained the exact string
Backlog. The action validates single-select values by name, so the stale value causes a hard failure. Routing to the existingSomedayoption restores the intended backlog placement without changing triggers, permissions, labels, project selection, or active-work statuses.