Skip to content

mergify: use defaults #16659

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 2 commits into from
Apr 16, 2025
Merged

mergify: use defaults #16659

merged 2 commits into from
Apr 16, 2025

Conversation

v1v
Copy link
Member

@v1v v1v commented Apr 16, 2025

Motivation/summary

tidy up common values and use the top-level defaults.

Checklist

For functional changes, consider:

  • Is it observable through the addition of either logging or metrics?
  • Is its use being published in telemetry to enable product improvement?
  • Have system tests been added to avoid regression?

How to test these changes

Related issues

@v1v v1v added the backport-skip Skip notification from the automated backport with mergify label Apr 16, 2025
@v1v v1v requested review from a team April 16, 2025 15:30
@v1v v1v self-assigned this Apr 16, 2025
@v1v v1v requested a review from a team as a code owner April 16, 2025 15:30
@v1v v1v merged commit 4d77dda into elastic:main Apr 16, 2025
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-skip Skip notification from the automated backport with mergify
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants