Skip to content

Add mutation commit message

Mergify / Summary succeeded Dec 19, 2024 in 1s

1 potential rule

Rule: Automatic merge on approval (merge)

  • #approved-reviews-by>=1
  • any of: [πŸ›‘ GitHub branch protection]
    • check-neutral = Test (.NET Framework)
    • check-skipped = Test (.NET Framework)
    • check-success = Test (.NET Framework)
  • any of: [πŸ›‘ GitHub branch protection]
    • check-neutral = Test (Examples)
    • check-skipped = Test (Examples)
    • check-success = Test (Examples)
  • any of: [πŸ›‘ GitHub branch protection]
    • check-neutral = Test (MacOS)
    • check-skipped = Test (MacOS)
    • check-success = Test (MacOS)
  • any of: [πŸ›‘ GitHub branch protection]
    • check-neutral = Test (Windows)
    • check-skipped = Test (Windows)
    • check-success = Test (Windows)
  • any of: [πŸ›‘ GitHub branch protection]
    • check-neutral = Test (Ubuntu)
    • check-skipped = Test (Ubuntu)
    • check-success = Test (Ubuntu)
  • any of: [πŸ›‘ GitHub branch protection]
    • check-neutral = SonarCloud Code Analysis
    • check-skipped = SonarCloud Code Analysis
    • check-success = SonarCloud Code Analysis
  • #commits-behind = 0 [πŸ›‘ GitHub branch protection]
  • #review-threads-unresolved = 0 [πŸ›‘ GitHub branch protection]
  • -closed [πŸ“Œ merge requirement]
  • -conflict [πŸ“Œ merge requirement]
  • -draft [πŸ“Œ merge requirement]
  • any of: [πŸ“Œ merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [πŸ›‘ GitHub branch protection]
    • check-success = Codacy Static Code Analysis
    • check-neutral = Codacy Static Code Analysis
    • check-skipped = Codacy Static Code Analysis
  • any of: [πŸ›‘ GitHub branch protection]
    • check-success = Testably/Conventional-Commits
    • check-neutral = Testably/Conventional-Commits
    • check-skipped = Testably/Conventional-Commits

πŸ’–Β Β 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 for Renovate pull requests (merge)

  • author=renovate[bot]
  • any of: [πŸ›‘ GitHub branch protection]
    • check-neutral = Test (.NET Framework)
    • check-skipped = Test (.NET Framework)
    • check-success = Test (.NET Framework)
  • any of: [πŸ›‘ GitHub branch protection]
    • check-neutral = Test (Examples)
    • check-skipped = Test (Examples)
    • check-success = Test (Examples)
  • any of: [πŸ›‘ GitHub branch protection]
    • check-neutral = Test (MacOS)
    • check-skipped = Test (MacOS)
    • check-success = Test (MacOS)
  • any of: [πŸ›‘ GitHub branch protection]
    • check-neutral = Test (Windows)
    • check-skipped = Test (Windows)
    • check-success = Test (Windows)
  • any of: [πŸ›‘ GitHub branch protection]
    • check-neutral = Test (Ubuntu)
    • check-skipped = Test (Ubuntu)
    • check-success = Test (Ubuntu)
  • any of: [πŸ›‘ GitHub branch protection]
    • check-neutral = SonarCloud Code Analysis
    • check-skipped = SonarCloud Code Analysis
    • check-success = SonarCloud Code Analysis
  • #commits-behind = 0 [πŸ›‘ GitHub branch protection]
  • #review-threads-unresolved = 0 [πŸ›‘ GitHub branch protection]
  • -closed [πŸ“Œ merge requirement]
  • -conflict [πŸ“Œ merge requirement]
  • -draft [πŸ“Œ merge requirement]
  • any of: [πŸ“Œ merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [πŸ›‘ GitHub branch protection]
    • check-success = Codacy Static Code Analysis
    • check-neutral = Codacy Static Code Analysis
    • check-skipped = Codacy Static Code Analysis
  • any of: [πŸ›‘ GitHub branch protection]
    • check-success = Testably/Conventional-Commits
    • check-neutral = Testably/Conventional-Commits
    • check-skipped = Testably/Conventional-Commits
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