-
Notifications
You must be signed in to change notification settings - Fork 42
ci(mergify): upgrade configuration to current format #712
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
base: main
Are you sure you want to change the base?
Conversation
.github/mergify.yml
Outdated
| update_method: rebase | ||
|
|
||
| queue_rules: | ||
| - name: duplicated default from API changes needs approval from a contributor and |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nixpanic I think we need to adapt the new config to the existing rule we have for API instead of having this new one, right?
1afe647 to
0ccc7fa
Compare
0ccc7fa to
ff97fcf
Compare
| request_reviews: | ||
| users_from_teams: | ||
| - "@csi-addons/kubernetes-csi-addons-contributors" | ||
| - name: API changes needs approval from a contributor and a reviewer + merge after |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This rule looks weird...
|
@Mergifyio rebase |
☑️ Nothing to do, the required conditions are not met
|
Hey there! 👋
We've noticed that your Mergify configuration is using some deprecated fields.
No worries—we've got your back! This automated PR updates your config to align with the newest standards, ensuring everything keeps running smoothly.
Do not procrastinate! You must upgrade your configuration before 2025-01-31, otherwise your configuration will stop working.
What's Changed?
pull_request_rules → actions → queue → update_method: To ease the configuration of queues, we are moving this attribute in thequeue_rulesdefinition. (deadline: 2025-01-31)pull_request_rules → actions → queue → merge_method: To ease the configuration of queues, we are moving this attribute in thequeue_rulesdefinition. (deadline: 2025-01-31)defaults → actions → queue → update_method: To ease the configuration of queues, we are moving this attribute in thequeue_rulesdefinition. (deadline: 2025-01-31)defaults → actions → queue → merge_method: To ease the configuration of queues, we are moving this attribute in thequeue_rulesdefinition. (deadline: 2025-01-31)Why This Matters
Keeping your configuration up-to-date means you'll benefit from the latest features and improvements Mergify has to offer. Plus, it helps prevent any unexpected hiccups down the road.
Got Questions? We've Got Answers! 🙌
Is this update safe to merge?
Absolutely! We've made sure the changes are compatible with your current setup. Your workflows should continue to work just as before—if not better!
Do I need to do anything special after merging?
Nope! Just merge this PR, and you're all set. If you have any custom configurations, it's a good idea to give them a quick look to ensure everything's in order.
What if I run into issues or have concerns?
We're here to help! Feel free to reach out to our support team anytime.
Thanks for being awesome and keeping your configuration up-to-date! If you have any thoughts or need a hand, don't hesitate to let us know.
Happy merging! 🎉