Skip to content

feat: OpenSpec sync + issue-triage reusable workflows#64

Open
rubenvdlinde wants to merge 4 commits into
mainfrom
feature/openspec-project-sync
Open

feat: OpenSpec sync + issue-triage reusable workflows#64
rubenvdlinde wants to merge 4 commits into
mainfrom
feature/openspec-project-sync

Conversation

@rubenvdlinde
Copy link
Copy Markdown
Contributor

Summary

Brings the two reusable workflows that have been sitting on feature/openspec-project-sync for a while into a real PR for review.

  • .github/workflows/openspec-sync.yml — reusable workflow for syncing OpenSpec proposals/specs across repos.
  • .github/workflows/issue-triage.yml — auto-triages new issues (and a backlog-triage job for existing untriaged ones); uses the triggering branch for file links instead of the default branch.

Commits

  • fd13bb8 feat: Add OpenSpec sync and issue triage reusable workflows
  • c19b609 feat: Add backlog-triage job for existing untriaged issues
  • 47a8dfa fix: Remove Triage status from issue-triage workflow
  • ed13d49 fix: Use triggering branch for file links instead of default branch

Context

Surfaced during the .github consolidation pass: branch had 4 commits ahead of main but no PR, leaving the workflows undeployed. Opening for review/merge or close decision.

Adds two reusable workflows for the OpenSpec project board:

- openspec-sync.yml: Scans openspec/changes/ directories, creates/updates
  GitHub issues per change, tracks phase progression on the project board
- issue-triage.yml: Auto-triages new issues to the board, assigns reviewers,
  handles triage label decisions (accept, wontfix, duplicate, needs-info)
The triage workflow now supports a backlog-existing input that scans
all open issues without triage labels and adds them to the project
board in the Triage column.
Triage issues should have no Status value — they appear on the
separate Triage view, not on the Status board columns.
Specs travel development -> beta -> main, so links should point
to the branch that triggered the sync.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant