github-project

To create a GitHub Project v2 schema for plan-to-issues projection, run a deterministic GraphQL workflow that provisions the standard execution board and enforces required single-select fields like Status, ItemType, and DispatchMode.

The best way to ensure required fields exist in a GitHub Project v2 is to use an automation script that validates and enforces specific single-select, text, number, and date fields such as AutomationState and Risk with correct option sets.

You validate standard saved views in a GitHub Project v2 by running a verification workflow that checks for the provision of canonical views used for dispatch, runtime flow, epics, dependencies, review queue, and audits.

Yes, you need the gh CLI installed because the automation script uses it to execute GraphQL API calls, which deterministically create or verify the project board schema and saved views.

Yes, you can reuse an existing GitHub Project v2 for local issue-to-PR automation runtime review, provided the project has the correct shape with the required fields and standard saved views already configured.

Your GitHub Project v2 needs a specific schema with fields like DispatchMode and AutomationState to maintain an accurate dispatch queue and ensure reliable local issue-to-PR automation runtime execution.