Skip to content

fix(ci): restore GitHub issue project sync#9740

Open
tianmind-studio wants to merge 1 commit into
BasedHardware:mainfrom
tianmind-studio:codex/fix-project-sync-status
Open

fix(ci): restore GitHub issue project sync#9740
tianmind-studio wants to merge 1 commit into
BasedHardware:mainfrom
tianmind-studio:codex/fix-project-sync-status

Conversation

@tianmind-studio

@tianmind-studio tianmind-studio commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

What changed and why

Replace the removed Backlog value in the GitHub Issue Sync workflow with the project's current backlog-equivalent Someday status. 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

  • Inspected failed GitHub Issue Sync run 29356714415, which reports that Backlog does not exist and lists Someday, Next Week, TODO (This week), In progress, In review, and Done as the available values.
  • Confirmed from workflow history that Backlog replaced the original to-do status specifically to route synced issues into the backlog, making Someday the current semantic equivalent.
  • actionlint -shellcheck= .github/workflows/main.yml
  • Passed diff hygiene, architecture guardrails, product invariants, desktop changelog, deferred-work marker, lifecycle header, version-prefixed filename, and backend workflow contract checks.
  • The deployment secret-boundary check passes when repository-relative paths are normalized. Its native Windows invocation currently false-fails even with --base HEAD because 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 existing Someday option restores the intended backlog placement without changing triggers, permissions, labels, project selection, or active-work statuses.

Review in cubic

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.
@Git-on-my-level Git-on-my-level added workflow-review Needs maintainer review for workflow, automation, hooks, or CI behavior needs-maintainer-review Needs human maintainer review before merge labels Jul 14, 2026
@Git-on-my-level

Copy link
Copy Markdown
Collaborator

Thanks for the focused CI/workflow repair. I reviewed the actual diff against the linked failure in #9736: this only changes the Project V2 Status value used by .github/workflows/main.yml from Backlog to Someday, which matches the status list shown in the failing issue-sync runs and preserves the existing trigger/token/label behavior.

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 Someday is the intended backlog-equivalent bucket in project 1 and then rerun/observe the next qualifying issue sync after merge.


by AI on behalf of David — if you need David’s attention urgently, please @Git-on-my-level and escalate with need human response.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-maintainer-review Needs human maintainer review before merge workflow-review Needs maintainer review for workflow, automation, hooks, or CI behavior

Projects

None yet

Development

Successfully merging this pull request may close these issues.

GitHub Issue Sync targets removed Backlog project status

2 participants