ci(mergify): upgrade configuration to current format - #146
Conversation
|
Merge ProtectionsYour pull request matches the following merge protections and will not be merged until they are valid. 🟢 📃 Configuration Change RequirementsWonderful, this rule succeeded.Mergify configuration change
|
🦙 MegaLinter status:
|
| Descriptor | Linter | Files | Fixed | Errors | Elapsed time |
|---|---|---|---|---|---|
| ✅ EDITORCONFIG | editorconfig-checker | 1 | 0 | 0.01s | |
| ✅ REPOSITORY | checkov | yes | no | 15.92s | |
| ✅ REPOSITORY | gitleaks | yes | no | 6.71s | |
| ✅ REPOSITORY | git_diff | yes | no | 0.03s | |
| ✅ REPOSITORY | secretlint | yes | no | 2.56s | |
| ✅ REPOSITORY | trivy-sbom | yes | no | 2.53s | |
| ✅ REPOSITORY | trufflehog | yes | no | 4.05s | |
| prettier | 1 | 1 | 0.48s | ||
| ✅ YAML | yamllint | 1 | 0 | 0.42s |
See detailed report in MegaLinter reports
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff
MegaLinter is graciously provided by
a772c7a to
d6b907b
Compare
|
Merge Protections🟢 Merge protection satisfied — ready to merge. Show 1 satisfied protection🟢 📃 Configuration Change RequirementsMergify configuration change
|
3 similar comments
Merge Protections🟢 Merge protection satisfied — ready to merge. Show 1 satisfied protection🟢 📃 Configuration Change RequirementsMergify configuration change
|
Merge Protections🟢 Merge protection satisfied — ready to merge. Show 1 satisfied protection🟢 📃 Configuration Change RequirementsMergify configuration change
|
Merge Protections🟢 Merge protection satisfied — ready to merge. Show 1 satisfied protection🟢 📃 Configuration Change RequirementsMergify configuration change
|
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 2026-07-31, otherwise your configuration will stop working.
What's Changed?
{{ author }}/{{ merged_by }}assignee templates are deprecated. Use the canonical{{ author }}(and{{ merged_by }}for copy/backport) form, which Mergify resolves statically without templating. (deadline: 2026-09-30)merge_protections_settings.reporting_methodis changing fromcheck-runstodeployments. Your configuration has been updated to explicitly setcheck-runsto preserve current behavior. (deadline: 2026-07-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! 🎉