-
Notifications
You must be signed in to change notification settings - Fork 33
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.
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
O11Y-2859: Disable code coverage comments on pull requests #108
Conversation
Security InsightsNo security relevant content was detected by automated scans. Action Items
Questions or Comments? Reach out on Slack: #support-infosec. |
Public API ChangesNo changes to the public API found for commit 3a5f4f5 Showing results for 3a5f4f5
Last edited UTC May 02 at 20:52:49 |
Coverage after merging O11Y-2859 into master will be
Coverage Report
|
@@ -8,6 +8,9 @@ on: | |||
pull_request: | |||
branches: | |||
- '*' | |||
concurrency: | |||
group: opentelemetry-coverage-${{ github.ref }}-1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This ensures that when pushing commits during a short period, only the last commit pushed receives a full CI run. Prior CI runs will be cancelled.
strategy: | ||
matrix: | ||
# Don't run on newer SDKs until we're able to get on analyzer 1.x, | ||
# since our current analyzer version range results in build failures | ||
# when analysis hits the `<<<` operator. | ||
# sdk: [ 2.13.4, stable, dev ] | ||
sdk: [ 2.13.4 ] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note to selves, we should get back to the point where we can run CI on 2.18 as well as the latest 2.x and eventually 3.0
QA +1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 from RM
Which problem is this PR solving?
The CI for this repo depends on the Github token when posting code coverage info to the pull request. When 3rd parties propose changes, the CI fails because the Github token is not available to those 3rd parties.
Fixes # (issue)
Short description of the change
How Has This Been Tested?
The CI on this pr can confirm these changes will not disrupt the CI workflow.