Skip to content

docs: removed erroneous content from Testably section in README - #1349

Merged
vbreuss merged 1 commit into
TestableIO:mainfrom
HarrisonTCodes:docs/readme-testably-section-cleanup
Oct 8, 2025
Merged

vbreuss merged 1 commit into
TestableIO:mainfrom
HarrisonTCodes:docs/readme-testably-section-cleanup

docs: removed erroneous content from Testably section in README

bc13169
Select commit
Loading
Failed to load commit list.
This check has been archived and is scheduled for deletion. Learn more about checks retention
Mergify / Summary succeeded Oct 8, 2025 in 1s

1 potential rule

⚠️ The pull request has been merged by @vbreuss

Rule: Automatic merge on approval (merge)

  • -closed [📌 merge requirement]
  • #approved-reviews-by>=1
  • #commits-behind = 0 [🛡 GitHub repository ruleset rule]
  • #review-threads-unresolved = 0 [🛡 GitHub repository ruleset rule]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🛡 GitHub repository ruleset rule]
    • check-success = Unit tests (macos-latest)
    • check-neutral = Unit tests (macos-latest)
    • check-skipped = Unit tests (macos-latest)
  • any of: [🛡 GitHub repository ruleset rule]
    • check-success = Unit tests (ubuntu-latest)
    • check-neutral = Unit tests (ubuntu-latest)
    • check-skipped = Unit tests (ubuntu-latest)
  • any of: [🛡 GitHub repository ruleset rule]
    • check-success = Unit tests (windows-latest)
    • check-neutral = Unit tests (windows-latest)
    • check-skipped = Unit tests (windows-latest)
  • any of: [🛡 GitHub repository ruleset rule]
    • check-success = API tests
    • check-neutral = API tests
    • check-skipped = API tests
  • any of: [🛡 GitHub repository ruleset rule]
    • check-success = Testably/Conventional-Commits
    • check-neutral = Testably/Conventional-Commits
    • check-skipped = Testably/Conventional-Commits

1 not applicable rule

Rule: Automatic merge for Renovate pull requests (merge)

  • -closed [📌 merge requirement]
  • author=renovate[bot]
  • #commits-behind = 0 [🛡 GitHub repository ruleset rule]
  • #review-threads-unresolved = 0 [🛡 GitHub repository ruleset rule]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🛡 GitHub repository ruleset rule]
    • check-success = Unit tests (macos-latest)
    • check-neutral = Unit tests (macos-latest)
    • check-skipped = Unit tests (macos-latest)
  • any of: [🛡 GitHub repository ruleset rule]
    • check-success = Unit tests (ubuntu-latest)
    • check-neutral = Unit tests (ubuntu-latest)
    • check-skipped = Unit tests (ubuntu-latest)
  • any of: [🛡 GitHub repository ruleset rule]
    • check-success = Unit tests (windows-latest)
    • check-neutral = Unit tests (windows-latest)
    • check-skipped = Unit tests (windows-latest)
  • any of: [🛡 GitHub repository ruleset rule]
    • check-success = API tests
    • check-neutral = API tests
    • check-skipped = API tests
  • any of: [🛡 GitHub repository ruleset rule]
    • 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