📖 Fix SBOM-Everywhere link #4334
Open
+1
−1
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
I noticed this link was broken (404) when trying to follow it. Signed-off-by: Evan Anderson <evan@stacklok.com>
There was a problem hiding this comment.
Thanks for the PR, two comments:
- The old link seems to resolve fine for me
- If you still want to go forward with the change, see our CONTRIBUTING.md for instructions on how to modify this file. (Or the new version from 📖 explicitly state both check documentation files are committed #4317 which hasn't been merged yet)
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.
I noticed this link was broken (404) when trying to follow it.
What kind of change does this PR introduce?
Docs Update
What is the current behavior?
404 on clicking the link
What is the new behavior (if this is a feature change)?**
Linking to a valid markdown document.
Which issue(s) this PR fixes
NONE
Special notes for your reviewer
Does this PR introduce a user-facing change?