Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modify labeler to consider issues with more than 3 services impacted as cross-provider #21081

Conversation

modular-magician
Copy link
Collaborator

Fixes #20818

  • I tested locally with some issue bodies and the results looked good
  • I chose not to include the backfill job: basically, the backfill job ignores issues with service/terraform, so the condition mentioned here would only be triggered after a ticket is created with < 4 services, and then more are added later, which is both unusual, and something we can handle manually.

Release Note Template for Downstream PRs (will be copied)

See Write release notes for guidance.


Derived from GoogleCloudPlatform/magic-modules#12863

…as cross-provider (hashicorp#12863)

[upstream:cc59b927154fcc3a61b2ee06b6fc704444c0584a]

Signed-off-by: Modular Magician <magic-modules@google.com>
@modular-magician modular-magician requested a review from a team as a code owner January 28, 2025 19:50
@modular-magician modular-magician merged commit d38bcf8 into hashicorp:main Jan 28, 2025
4 checks passed
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.

Make issue labeler apply service/terraform label if more than 3 services are impacted
1 participant