docs: fix security reporting links to use absolute repo URLs#13
Merged
Conversation
SECURITY.md referenced the Security tab without an actual link, and the bypass issue form used a relative [SECURITY.md](../blob/main/SECURITY.md) that resolves wrong from the issue-creation page (landed at Babyhamsta/security.md, not the repo). Point both at absolute URLs: the private-advisory page and the repo SECURITY.md.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
SECURITY.md had no actual link to the reporting page, and the bypass issue form's relative
../blob/main/SECURITY.mdresolves wrong from the issue-creation page (lands atBabyhamsta/security.md). Both now point at absolute URLs (the private-advisory page + repo SECURITY.md).