fix(website): migrate Pages URLs to OWASP - #341
Merged
Merged
Conversation
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
Signed-off-by: ritiksah141 <ritiksah141@gmail.com>
ritiksah141
force-pushed
the
fix/owasp-pages-migration
branch
from
September 16, 2026 01:01
b27b23c to
908153d
Compare
TFT444
approved these changes
Sep 16, 2026
10 tasks
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
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.
Summary
openshield-orgidentity toOWASPOWASP/openshieldmainbranch while retaining PR validation fordevandmainopenshield-orgis reintroduced into website source filesVerification
npm run check --prefix websitehttps://owasp.github.io/openshield/openshield-orgreferencesrefs/heads/maincan upload and deploy the Pages artifactRequired administrator action
This PR does not change repository administration settings. An OWASP repository administrator must set
Settings > Pages > Build and deployment > SourcetoGitHub Actions, then rerun thewebsiteworkflow frommain. Until that is done,actions/deploy-pageswill continue failing with HTTP 404 and GitHub will keep serving the legacymainPages build.