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

Bump dotenv from 16.4.1 to 16.4.3 #5534

Merged
merged 1 commit into from
Feb 13, 2024

Bump dotenv from 16.4.1 to 16.4.3

68abb5c
Select commit
Loading
Failed to load commit list.
Merged

Bump dotenv from 16.4.1 to 16.4.3 #5534

Bump dotenv from 16.4.1 to 16.4.3
68abb5c
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Feb 13, 2024 in 4s

1 rule matches and 1 potential rule

⚠️ The pull request has been merged by @github-actions[bot]

Rule: automatic merge for master when reviewed and CI passes (queue)

  • label=ready-to-merge
  • -draft [📌 queue requirement]
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • #approved-reviews-by>=1 [🛡 GitHub branch protection]
      • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
      • any of: [🛡 GitHub branch protection]
        • check-success=build
        • check-neutral=build
        • check-skipped=build
      • any of: [🛡 GitHub branch protection]
        • check-success=SonarCloud Code Analysis
        • check-neutral=SonarCloud Code Analysis
        • check-skipped=SonarCloud Code Analysis

✅ Rule: delete head branch after merge (delete_head_branch)

  • closed [📌 delete_head_branch requirement]
  • merged

💖  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: ask developers to resolve conflict (comment)

  • -author~=^dependabot(|-preview)\[bot\]$
  • conflict
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