8000 Add excluded emails to mergegate configuration by AAraKKe · Pull Request #20523 · DataDog/integrations-core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Add excluded emails to mergegate configuration #20523

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

Merged
merged 1 commit into from
Jun 17, 2025
Merged

Conversation

AAraKKe
Copy link
Contributor
@AAraKKe AAraKKe commented Jun 17, 2025

What does this PR do?

This PR adds excluded emails for our bots for the mergegate validation.

The emails are for the bot that creates PRs from actions and the email used from the release pipeline.

Motivation

Mergegate enforces commit signing before reaching our default branch

Review checklist (to be filled by reviewers)

  • Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
  • Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
  • If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

8000
@AAraKKe AAraKKe requested a review from a team as a code owner June 17, 2025 09:23
@AAraKKe AAraKKe added the qa/skip-qa Automatically skip this PR for the next QA label Jun 17, 2025
@AAraKKe AAraKKe added this pull request to the merge queue Jun 17, 2025
Merged via the queue into master with commit 3a65eb4 Jun 17, 2025
27 of 28 checks passed
@AAraKKe AAraKKe deleted the aarakke/mergegate branch June 17, 2025 10:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
qa/skip-qa Automatically skip this PR for the next QA team/agent-integrations
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0