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): update dependency @types/dockerode to v3.3.29 - autoclosed #1260

Closed
wants to merge 1 commit into from

chore(deps): update dependency @types/dockerode to v3.3.29

514e1b4
Select commit
Loading
Failed to load commit list.
Closed

chore(deps): update dependency @types/dockerode to v3.3.29 - autoclosed #1260

chore(deps): update dependency @types/dockerode to v3.3.29
514e1b4
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded May 17, 2024 in 0s

1 rule matches and 2 potential rules

Rule: delete head branch after merge (delete_head_branch)

  • merged
  • closed [πŸ“Œ delete_head_branch requirement]

βœ… Rule: automatic label Renovate pull requests (label)

  • author=renovate[bot]

Rule: automatic merge for Renovate pull requests (merge)

  • #approved-reviews-by>=1 [πŸ›‘ GitHub branch protection]
  • #commits-behind=0 [πŸ›‘ GitHub branch protection]
  • -closed [πŸ“Œ merge requirement]
  • #changes-requested-reviews-by=0 [πŸ›‘ GitHub branch protection]
  • -conflict [πŸ“Œ merge requirement]
  • -draft [πŸ“Œ merge requirement]
  • author=renovate[bot]
  • check-success=test
  • any of: [πŸ“Œ merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed
  • any of: [πŸ›‘ GitHub branch protection]
    • check-success=test
    • check-neutral=test
    • check-skipped=test

πŸ’–Β Β 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: branch name check (close, label)

  • -closed
  • head~=^(master|main)/
  • -merged
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