Skip to content

chore: Bump Testably.Abstractions.Testing from 7.0.2 to 7.1.0 - #196

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/Testably.Abstractions.Testing-7.1.0
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/Testably.Abstractions.Testing-7.1.0

chore: Bump Testably.Abstractions.Testing from 7.0.2 to 7.1.0

833ef82
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Sep 28, 2026 in 1s

1 potential rule

Rule: Auto-merge Dependabot PRs into main (merge)

  • -closed [📌 merge requirement]
  • check-success = Unit tests (macos-latest)
  • check-success = Unit tests (ubuntu-latest)
  • check-success = Unit tests (windows-latest)
  • any of: [🛡 GitHub repository ruleset rule main]
    • check-neutral = @github-actions/Test Results
    • check-skipped = @github-actions/Test Results
    • check-success = @github-actions/Test Results
  • any of: [🛡 GitHub repository ruleset rule main]
    • check-neutral = @github-actions/Unit tests (macos-latest)
    • check-skipped = @github-actions/Unit tests (macos-latest)
    • check-success = @github-actions/Unit tests (macos-latest)
  • any of: [🛡 GitHub repository ruleset rule main]
    • check-neutral = @github-actions/Unit tests (ubuntu-latest)
    • check-skipped = @github-actions/Unit tests (ubuntu-latest)
    • check-success = @github-actions/Unit tests (ubuntu-latest)
  • any of: [🛡 GitHub repository ruleset rule main]
    • check-neutral = @github-actions/Unit tests (windows-latest)
    • check-skipped = @github-actions/Unit tests (windows-latest)
    • check-success = @github-actions/Unit tests (windows-latest)
  • #review-threads-unresolved = 0 [🛡 GitHub repository ruleset rule main]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • author = dependabot[bot]
  • base = main
  • check-success = API tests
  • github-review-approved [🛡 GitHub repository ruleset rule main]
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = @mergify/Configuration changed
    • check-success = @mergify/Configuration has been deleted
  • any of: [🛡 GitHub repository ruleset rule main]
    • check-success = @github-actions/API tests
    • check-neutral = @github-actions/API tests
    • check-skipped = @github-actions/API tests
  • any of: [🛡 GitHub repository ruleset rule main]
    • check-success = @github-actions/Mutation tests
    • check-neutral = @github-actions/Mutation tests
    • check-skipped = @github-actions/Mutation tests
  • any of: [🛡 GitHub repository ruleset rule main]
    • check-success = @github-actions/Publish Tests Results
    • check-neutral = @github-actions/Publish Tests Results
    • check-skipped = @github-actions/Publish Tests Results
  • any of: [🛡 GitHub repository ruleset rule main]
    • check-success = Testably/Conventional-Commits
    • check-neutral = Testably/Conventional-Commits
    • check-skipped = Testably/Conventional-Commits
  • any of: [🛡 GitHub repository ruleset rule main]
    • check-success = @github-actions/Benchmarks
    • check-neutral = @github-actions/Benchmarks
    • check-skipped = @github-actions/Benchmarks
  • any of: [🛡 GitHub repository ruleset rule main]
    • check-skipped = @github-actions/Static code analysis
    • check-neutral = @github-actions/Static code analysis
    • check-success = @github-actions/Static code analysis

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