Skip to content

ci: fix pr-triage-manager team reference to aws-cdk-team - #38203

Merged
mergify[bot] merged 1 commit into
mainfrom
fix/pr-triage-manager-team-reference
Jun 25, 2026
Merged

ci: fix pr-triage-manager team reference to aws-cdk-team#38203
mergify[bot] merged 1 commit into
mainfrom
fix/pr-triage-manager-team-reference

Conversation

@ozelalisen

Copy link
Copy Markdown
Member

Issue # (if applicable)

Closes #38197.

Reason for this change

The pr-triage-manager job requested reviewers from team aws-cdk-owners, which does not exist in the aws org. Every PR from a beginning contributor failed with Reviews may only be requested from collaborators, leaving 25+ PRs with a failing check.

Description of changes

Updated teamReviewers in .github/workflows/issue-label-assign.yml from the non-existent aws-cdk-owners to the existing aws-cdk-team.

Describe any new or updated permissions being added

None.

Description of how you validated changes

CI-only change; verified aws-cdk-owners was the sole reference in .github/ and corrected it to a valid team.

Checklist


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

The pr-triage-manager job referenced the non-existent team
"aws-cdk-owners" when requesting reviewers, causing every PR from
beginning contributors to fail with "Reviews may only be requested
from collaborators". Point teamReviewers at the existing aws-cdk-team.

Closes #38197
@github-actions github-actions Bot added effort/medium Medium work item – several days of effort p1 labels Jun 25, 2026
@mergify mergify Bot added the contribution/core This is a PR that came from AWS. label Jun 25, 2026
@mergify
mergify Bot temporarily deployed to automation June 25, 2026 12:20 Inactive
@mergify
mergify Bot temporarily deployed to automation June 25, 2026 12:20 Inactive
@mergify

mergify Bot commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

Queued — the merge queue status continues in this comment ↓.

@mergify

mergify Bot commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

@mergify

mergify Bot commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

Merge Queue Status

  • Entered queue2026-06-25 13:05 UTC · Rule: default-squash · triggered by rule automatic merge
  • Checks skipped · PR is already up-to-date
  • Merged2026-06-25 13:05 UTC · at bc799d1482f6da77881a72e70db12b8479eab992 · squash

This pull request spent 17 seconds in the queue, including 2 seconds running CI.

Required conditions to merge
  • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • any of [🛡 GitHub branch protection]:
    • check-success = validate-pr
    • check-neutral = validate-pr
    • check-skipped = validate-pr
  • any of [🛡 GitHub branch protection]:
    • check-success = build
    • check-neutral = build
    • check-skipped = build

@mergify
mergify Bot merged commit fa5122a into main Jun 25, 2026
32 of 34 checks passed
@mergify
mergify Bot deleted the fix/pr-triage-manager-team-reference branch June 25, 2026 13:05
@github-actions

Copy link
Copy Markdown
Contributor

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.

@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Jun 25, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

contribution/core This is a PR that came from AWS. effort/medium Medium work item – several days of effort p1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug(ci): pr-triage-manager fails on all beginning-contributor PRs — references non-existent team aws-cdk-owners

3 participants