status-workflow

Automate GitHub Projects v2 status transitions by resolving project item and option IDs to set the single-select Status field for an issue. This workflow uses GraphQL queries to verify updates and detect silent failures or permission issues during automation.

Yes, you can add or remove labels when moving an issue between Status field options. The workflow performs status field mutations and optionally manages issue annotations alongside the transition to keep project boards synchronized.

Yes, you need the gh CLI and jq to update project board statuses. A valid GH_TOKEN and board-scanner variables like PROJECT_ID, STATUS_FIELD_ID, and FIELD_DATA are also required to execute the GraphQL queries for verification.

The best way to verify GitHub Projects v2 status updates is by confirming changes with GraphQL queries. This verification mechanism detects silent failures or permission issues immediately after applying status field mutations to project items.

Record attribution comments on team project boards by posting role or emoji annotations during workflow automation. This tracks who performed the status transition while automatically moving issues across project board columns.

GitHub Projects v2 status field mutations may fail due to silent failures or permission issues. Resolve project item and option IDs correctly, ensure a valid GH_TOKEN is set, and use GraphQL queries to verify that updates are applied successfully.