Skip to content

ci: Add issue triage workflow - #590

Merged
ayushiahjolia merged 1 commit into
mainfrom
add-issue-triage-workflow
Aug 4, 2026
Merged

ci: Add issue triage workflow#590
ayushiahjolia merged 1 commit into
mainfrom
add-issue-triage-workflow

Conversation

@ayushiahjolia

Copy link
Copy Markdown
Contributor

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Issue Link, if available

Followup on aws/aws-durable-execution-ci#6

Description

Adds a GitHub Actions workflow that automatically triages newly opened issues by delegating to the shared reusable workflow in aws/aws-durable-execution-ci.

Demo/Screenshots

N/A

Checklist

  • I have filled out every section of the PR template
  • I have thoroughly tested this change

Testing

Unit Tests

Have unit tests been written for these changes? N/A

Integration Tests

Have integration tests been written for these changes? N/A

Examples

Has a new example been added for the change? (if applicable) N/A

@ayushiahjolia
ayushiahjolia requested a review from a team August 4, 2026 21:21
@ayushiahjolia
ayushiahjolia temporarily deployed to ai-pr-review-runtime August 4, 2026 21:21 — with GitHub Actions Inactive
@ayushiahjolia
ayushiahjolia temporarily deployed to ai-pr-review-runtime August 4, 2026 21:21 — with GitHub Actions Inactive
@ayushiahjolia
ayushiahjolia merged commit c007642 into main Aug 4, 2026
14 checks passed
@ayushiahjolia
ayushiahjolia deleted the add-issue-triage-workflow branch August 4, 2026 21:25
@github-actions

github-actions Bot commented Aug 4, 2026

Copy link
Copy Markdown

Claude AI review

This PR adds a single CI workflow (.github/workflows/issue-triage.yml) that delegates issue triage to a pinned reusable workflow in aws/aws-durable-execution-ci. It touches no SDK source, so the correctness/typing/replay/serialization focus areas do not apply.

The change is well-formed and consistent with existing repo conventions:

  • Reusable workflow pinned to a full commit SHA (matches notify.yml, ai-pr-review.yml).
  • Top-level permissions: {} with least-privilege per-job issues: write.
  • Trigger issues: [opened] is appropriate for triage-on-open.

No actionable findings.

Residual test risk (cannot be confirmed from this diff, since the delegated logic lives in the referenced repo at the pinned SHA — worth a manual check against that reusable workflow):

  • .github/workflows/issue-triage.yml:15-19 — no secrets: inherit/explicit secrets: is passed; if the reusable triage workflow needs credentials (as ai-pr-review.yml does), it would fail at runtime.
  • .github/workflows/issue-triage.yml:16-18 — only issues: write is granted; if the reusable workflow requires OIDC (id-token: write) or contents: read, the missing permission would cause a runtime failure.

Neither is a defect in the diff itself.

Reviewed commit 771a7e7e7cd8d971d4b3cd1013c2bff4f3235d31. Workflow run

@github-actions

github-actions Bot commented Aug 4, 2026

Copy link
Copy Markdown

Codex AI review

No actionable findings. Residual risk: the pinned reusable workflow’s contract and runtime behavior were not locally executable or inspectable.

Reviewed commit 771a7e7e7cd8d971d4b3cd1013c2bff4f3235d31. Workflow run

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.

2 participants