Skip to content

feat(actions): add common issue lifecycle workflows#58

Open
uwe-mayer wants to merge 3 commits intomainfrom
feat/introduce-issue-workflows
Open

feat(actions): add common issue lifecycle workflows#58
uwe-mayer wants to merge 3 commits intomainfrom
feat/introduce-issue-workflows

Conversation

@uwe-mayer
Copy link
Copy Markdown

Summary

Introduces shared issue lifecycle workflows and documentation for use across all cloudoperators repositories.

New files:

  • ISSUE_LIFECYCLE.md — Single source of truth for the issue triage/refinement/backlog workflow
  • skills/issue-triage.md — AI agent skill for automated issue triage
  • workflows/issue-triage/action.yaml — Composite action: auto-labels needs-triage + posts welcome comment on new issues
  • workflows/issue-project-sync/action.yaml — Composite action: adds issues to project feat:(actions) share actions #9 when backlog label is applied

Updated:

  • CONTRIBUTING.md — Now references the shared ISSUE_LIFECYCLE.md

Setup required after merge:

  1. Create org-level secret GH_PROJECT_TOKEN (PAT with project + repo scopes) shared with: greenhouse, shoot-grafter, repo-guard, cloudctl, owner-label-injector
  2. Merge dependent PRs in consuming repos (they reference cloudoperators/common/workflows/...@main)

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a shared, organization-wide issue lifecycle process and two reusable composite actions to automate early issue hygiene (triage labeling + project intake) across cloudoperators repositories.

Changes:

  • Introduces issue-triage composite action + documentation to auto-label newly opened issues and post a welcome comment.
  • Introduces issue-project-sync composite action + documentation to add issues to org project #9 when the backlog label is applied.
  • Adds org-wide Issue Lifecycle + agent skill documentation and updates contributing guidelines to reference it.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 4 comments.

Show a summary per file
File Description
workflows/issue-triage/README.md Documents how to consume the issue triage composite action across repos.
workflows/issue-triage/action.yaml Implements labeling + welcome-comment automation for newly opened issues.
workflows/issue-project-sync/README.md Documents how to consume the project-sync composite action and required secret/labels.
workflows/issue-project-sync/action.yaml Implements GraphQL-based addition of labeled issues to org project #9.
skills/issue-triage.md Defines an agent “skill” playbook for consistent triage decisions/labels.
ISSUE_LIFECYCLE.md Defines the canonical issue workflow, labels, and lifecycle stages.
CONTRIBUTING.md Updates contributing guidance to point to the shared issue lifecycle doc.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread workflows/issue-triage/action.yaml Outdated
Comment thread workflows/issue-triage/README.md
Comment thread workflows/issue-project-sync/action.yaml Outdated
Comment thread ISSUE_LIFECYCLE.md
uwe-mayer added 3 commits May 8, 2026 13:35
Signed-off-by: uwe-mayer <uwe.mayer01@sap.com>
…ssions docs)

Signed-off-by: uwe-mayer <uwe.mayer01@sap.com>
Signed-off-by: uwe-mayer <uwe.mayer01@sap.com>
@uwe-mayer uwe-mayer force-pushed the feat/introduce-issue-workflows branch from 0293902 to bea5b90 Compare May 8, 2026 11:35
Comment on lines +18 to +20
with:
project-url: ${{ inputs.PROJECT_URL }}
github-token: ${{ inputs.GH_TOKEN }} No newline at end of file
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
with:
project-url: ${{ inputs.PROJECT_URL }}
github-token: ${{ inputs.GH_TOKEN }}
with:
project-url: ${{ inputs.PROJECT_URL }}
github-token: ${{ inputs.GH_TOKEN }}
labeled: needs-refinement

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.

3 participants