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

ci(mergify): upgrade configuration to current format (backport #1326) #1328

Closed
wants to merge 1 commit into from

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Nov 23, 2024

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 → merge_method: To ease the configuration of queues, we are moving this attribute in the queue_rules definition. (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! 🎉


This is an automatic backport of pull request #1326 done by Mergify.

* ci(mergify): upgrade configuration to current format

* Use mergify only for backporting

---------

Co-authored-by: Mergify <37929162+mergify[bot]@users.noreply.github.com>
Co-authored-by: Ivan Carvalho <[email protected]>
(cherry picked from commit eaee0b5)

# Conflicts:
#	.mergify.yml
Copy link
Contributor Author

mergify bot commented Nov 23, 2024

Cherry-pick of eaee0b5 has failed:

On branch mergify/bp/stable/0.15/pr-1326
Your branch is up to date with 'origin/stable/0.15'.

You are currently cherry-picking commit eaee0b5.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	new file:   .github/.mergify.yml

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by them: .mergify.yml

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@IvanIsCoding
Copy link
Collaborator

Closing as this was just a test

@coveralls
Copy link

Pull Request Test Coverage Report for Build 11989855735

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.004%) to 95.796%

Totals Coverage Status
Change from base Build 10166411235: 0.004%
Covered Lines: 18001
Relevant Lines: 18791

💛 - Coveralls

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants