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 lycheeverse/lychee-action action to v2 #430

Merged
merged 1 commit into from
Oct 11, 2024

chore(deps): update lycheeverse/lychee-action action to v2

95c97c8
Select commit
Loading
Failed to load commit list.
Merged

chore(deps): update lycheeverse/lychee-action action to v2 #430

chore(deps): update lycheeverse/lychee-action action to v2
95c97c8
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Oct 11, 2024 in 0s

1 potential rule

Rule: Automatic merge from renovate (queue)

  • -closed [πŸ“Œ queue requirement]
  • -conflict [πŸ“Œ queue requirement]
  • -draft [πŸ“Œ queue requirement]
  • check-success=Good to merge
  • any of:
    • author=renovate[bot]
    • label=file-sync
  • any of: [πŸ“Œ queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [πŸ”€ queue conditions]
    • all of: [πŸ“Œ queue conditions of queue deps-update]
      • any of: [πŸ›‘ GitHub branch protection]
        • check-success = Good to merge
        • check-neutral = Good to merge
        • check-skipped = Good to merge

πŸ’–Β Β 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: Automatic merge when CI passes (merge)

  • -closed [πŸ“Œ merge requirement]
  • author!=renovate[bot]
  • -conflict [πŸ“Œ merge requirement]
  • -draft [πŸ“Œ merge requirement]
  • check-success=Good to merge
  • any of: [πŸ“Œ merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [πŸ›‘ GitHub branch protection]
    • check-success = Good to merge
    • check-neutral = Good to merge
    • check-skipped = Good to merge
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