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

Empty tuple instead of None for PlatformInfo version properties fallthrough #4754

Rename news fragment

50d671b
Select commit
Loading
Failed to load commit list.
Merged

Empty tuple instead of None for PlatformInfo version properties fallthrough #4754

Rename news fragment
50d671b
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Nov 20, 2024 in 2s

no rules match, no planned actions

⚠️ The pull request has been merged by @abravalheri


💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!


1 not applicable rule

Rule: auto-merge (merge)

  • -closed [📌 merge requirement]
  • base=master
  • label=auto-merge
  • status-success=continuous-integration/appveyor/pr
  • status-success=continuous-integration/travis-ci/pr
  • status-success=deploy/netlify
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com