Skip to content

Conversation

zeitlinger
Copy link
Member

No description provided.

@zeitlinger zeitlinger requested a review from a team as a code owner October 8, 2025 16:16
@zeitlinger
Copy link
Member Author

@trask same approach as agent

Copy link

codecov bot commented Oct 8, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.16%. Comparing base (e6b9462) to head (4ead00b).

Additional details and impacted files
@@            Coverage Diff            @@
##               main    #7733   +/-   ##
=========================================
  Coverage     90.16%   90.16%           
  Complexity     7190     7190           
=========================================
  Files           814      814           
  Lines         21702    21702           
  Branches       2125     2125           
=========================================
  Hits          19568    19568           
  Misses         1467     1467           
  Partials        667      667           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Comment on lines +14 to +21
[tasks."lint:links"]
file = "https://raw.githubusercontent.com/open-telemetry/opentelemetry-java-contrib/refs/heads/main/.mise/tasks/lint/links.sh"

[tasks."lint:local-links"]
file = "https://raw.githubusercontent.com/open-telemetry/opentelemetry-java-contrib/refs/heads/main/.mise/tasks/lint/local-links.sh"

[tasks."lint:links-in-modified-files"]
file = "https://raw.githubusercontent.com/open-telemetry/opentelemetry-java-contrib/refs/heads/main/.mise/tasks/lint/links-in-modified-files.sh"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

probably ideally these files would live in this (the "core") repo, since that's the direction most of our other dependencies flow

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe the spec repo if the approach proves to be successful?

Either way, we'd have to adjust all repos that pull the files before we remove it in contrib

Co-authored-by: Trask Stalnaker <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants