Problem
The Issue Governance workflow failed on master while processing newly opened issue #266. The enforce job exited after gh project returned unknown owner type, so the workflow did not apply its required project and issue metadata. Issue #266 has since closed, but the workflow failure remains current for future new issues.
EARS requirements
- THE SYSTEM SHALL resolve the canonical organization project reliably in the issue-governance workflow.
- WHEN an issue is opened, THE SYSTEM SHALL add or find its project card exactly once and populate missing required metadata.
- IF the project owner lookup fails, THEN THE SYSTEM SHALL emit a bounded actionable error and leave the issue available for retry.
- WHILE a new issue lacks required metadata, THE SYSTEM SHALL avoid reporting successful governance.
Source and privacy
Spark email ID: 31332. Failed run: https://github.com/shipshitdev/skills/actions/runs/37583581577 . Trigger issue: #266 . Privacy classification: Public. Filed from Spark cross-project issue intake.
Affected components
.github/workflows/issue-governance.yml and its GitHub CLI project-owner lookup and item-add steps.
Implementation notes
Determine why the workflow's gh project lookup rejects the organization owner in GitHub Actions. Keep project and field IDs derived from verified project data, preserve idempotent card creation, and make failures diagnosable without exposing credentials.
Acceptance criteria
- THE SYSTEM SHALL resolve the existing
Dev Loop organization project in the workflow environment.
- WHEN a new issue opens, THE SYSTEM SHALL create or reuse one canonical project card and populate Status, Priority, and Type using valid options.
- IF project lookup fails, THEN THE SYSTEM SHALL fail with a clear owner/project diagnostic without creating duplicate cards.
Verification plan
Reproduce the lookup with the workflow's GitHub CLI version and permissions, run the focused governance workflow on a safe test issue or replay, then require a green current-head run with exactly one correctly populated project card.
Problem
The
Issue Governanceworkflow failed onmasterwhile processing newly opened issue #266. Theenforcejob exited aftergh projectreturnedunknown owner type, so the workflow did not apply its required project and issue metadata. Issue #266 has since closed, but the workflow failure remains current for future new issues.EARS requirements
Source and privacy
Spark email ID: 31332. Failed run: https://github.com/shipshitdev/skills/actions/runs/37583581577 . Trigger issue: #266 . Privacy classification: Public. Filed from Spark cross-project issue intake.
Affected components
.github/workflows/issue-governance.ymland its GitHub CLI project-owner lookup and item-add steps.Implementation notes
Determine why the workflow's
gh projectlookup rejects the organization owner in GitHub Actions. Keep project and field IDs derived from verified project data, preserve idempotent card creation, and make failures diagnosable without exposing credentials.Acceptance criteria
Dev Looporganization project in the workflow environment.Verification plan
Reproduce the lookup with the workflow's GitHub CLI version and permissions, run the focused governance workflow on a safe test issue or replay, then require a green current-head run with exactly one correctly populated project card.