feat: add initial benchmarks - #605

Rule: Automatic merge for Renovate pull requests (merge)

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

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