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

chore(deps-dev): bump the all group with 10 updates #438

Merged
merged 1 commit into from
Mar 4, 2024

chore(deps-dev): bump the all group with 10 updates

351b7da
Select commit
Loading
Failed to load commit list.
Merged

chore(deps-dev): bump the all group with 10 updates #438

chore(deps-dev): bump the all group with 10 updates
351b7da
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Mar 4, 2024 in 1s

2 potential rules

Rule: merge reviewed and built PRs (merge)

  • #approved-reviews-by>=1
  • -closed [📌 merge requirement]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • base=main
  • status-success=build (2.x)
  • status-success=build (3.x)
  • status-success=build (4.x)
  • status-success=license/cla
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed

Rule: automatic merge for Dependabot pull requests (merge)

  • -closed [📌 merge requirement]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • author~=^dependabot(|-preview)\[bot\]$
  • status-success=build (2.x)
  • status-success=build (3.x)
  • status-success=build (4.x)
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed

💖  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: merge reviewed PRs from the repo owner (merge)

  • -closed [📌 merge requirement]
  • author=dbartholomae
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • base=main
  • status-success=build (2.x)
  • status-success=build (3.x)
  • status-success=build (4.x)
  • 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