📖 fix invalid documentation link to SLSA #2073
Merged
Conversation
This file contains 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
natebwangsut
changed the title
|
Integration tests success for |
naveensrinivasan
approved these changes
Jul 19, 2022
azeemshaikh38
approved these changes
Jul 19, 2022
|
Thanks @natebwangsut! |
Codecov Report
@@ Coverage Diff @@
## main #2073 +/- ##
==========================================
+ Coverage 42.03% 44.53% +2.50%
==========================================
Files 92 92
Lines 7554 7554
==========================================
+ Hits 3175 3364 +189
+ Misses 4130 3934 -196
- Partials 249 256 +7 |
singhsaurabh
pushed a commit
to singhsaurabh/scorecard
that referenced
this pull request
Jul 25, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What kind of change does this PR introduce?
(Is it a bug fix, feature, docs update, something else?)
Special notes for your reviewer
Just fixing the invalid link on
README.mdDoes this PR introduce a user-facing change?
For user-facing changes, please add a concise, human-readable release note to
the
release-note(In particular, describe what changes users might need to make in their
application as a result of this pull request.)