Ci/coverage badge #191
Merged
Ci/coverage badge #191
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ust-sdk into ci/coverage-badge
Z9RTM
commented
May 18, 2025
| run: cargo llvm-cov --all-features | ||
| run: cargo llvm-cov --all-features --lcov --output-path lcov.info | ||
|
|
||
| - name: Generate coverage badge |
Contributor
Author
There was a problem hiding this comment.
Maybe the badge image will finally generate properly if we run this job on the main branch.
Contributor
Author
jokemanfire
approved these changes
May 19, 2025
Collaborator
|
Could you check it ,it looks like svg not effective, I think the path in readme has some problems. |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation and Context
This change implements a mechanism to nearly automate the process of displaying generated coverage badge images within the project's README.md.
#49 (comment)
How Has This Been Tested?
just run
act pull_request -j coverageBreaking Changes
no
Types of changes
Checklist
Additional context