Skip to content

Add option to use OpenTelemetry semantic conventions #148

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.

Sign up for GitHub

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

Draft
bpholt wants to merge 2 commits into
base: main
Choose a base branch
from

add useOpenTelemetrySemanticConventions option to server middleware

81b918b
Select commit
Loading
Failed to load commit list.
Draft

Add option to use OpenTelemetry semantic conventions #148

add useOpenTelemetrySemanticConventions option to server middleware
81b918b
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Dec 18, 2025 in 1s

1 rule matches and 4 potential rules

Rule: Label core PRs (label)

  • files~=^modules/core/

Rule: Label docs PRs (label)

  • files~=^modules/docs/

Rule: Label examples PRs (label)

  • files~=^modules/examples/

✅ Rule: Label http4s PRs (label)

  • files~=^modules/http4s/

Rule: Label mtl PRs (label)

  • files~=^modules/mtl/
💖  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: merge scala-steward's PRs (merge)

  • -draft [📌 merge requirement]
  • author=typelevel-steward[bot]
  • status-success=Test (ubuntu-22.04, 2.12, temurin@17, rootJS)
  • status-success=Test (ubuntu-22.04, 2.12, temurin@17, rootJVM)
  • status-success=Test (ubuntu-22.04, 2.12, temurin@17, rootNative)
  • status-success=Test (ubuntu-22.04, 2.13, temurin@17, rootJS)
  • status-success=Test (ubuntu-22.04, 2.13, temurin@17, rootJVM)
  • status-success=Test (ubuntu-22.04, 2.13, temurin@17, rootNative)
  • status-success=Test (ubuntu-22.04, 3, temurin@17, rootJS)
  • status-success=Test (ubuntu-22.04, 3, temurin@17, rootJVM)
  • status-success=Test (ubuntu-22.04, 3, temurin@17, rootNative)
  • any of:
    • body~=labels:.*early-semver-minor
    • body~=labels:.*early-semver-patch
  • -closed [📌 merge requirement]
  • -conflict [📌 merge requirement]
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
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

View more details on Mergify