From 4808c162eeb767b389f13b7cb2730f32c8563dba Mon Sep 17 00:00:00 2001 From: Eric Traut Date: Mon, 29 Jun 2026 11:10:38 -0700 Subject: [PATCH] [codex] auto-label AWS Bedrock issues (#30607) ## Summary AWS Bedrock issues currently fall under broader labels, which makes provider-specific reports harder to find. The issue tracker now has an `aws-bedrock` label, but the automated labeler does not know to apply it. Teach the issue labeler to select `aws-bedrock` for Amazon Bedrock provider or Bedrock Mantle issues while excluding generic AWS references. --- .github/workflows/issue-labeler.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/workflows/issue-labeler.yml b/.github/workflows/issue-labeler.yml index 2c4eb6aa6..0f11d2af5 100644 --- a/.github/workflows/issue-labeler.yml +++ b/.github/workflows/issue-labeler.yml @@ -78,6 +78,7 @@ jobs: 30. automations - Issues involving scheduled automation tasks or heartbeats. 31. pets - Issues involving pets avatars and animations. 32. agent - Fallback only for core agent loop or agent-related issues that do not fit app-server, connectivity, subagent, session, config, plan, computer-use, browser, memory, imagen, remote, performance, automations, or pets. + 33. aws-bedrock - Issues involving the Amazon Bedrock model provider or Bedrock Mantle. Do not use for unrelated AWS services or generic AWS mentions. Issue number: ${{ github.event.issue.number }}