Repository navigation
chore(www): migrate root .well-known/ to www/.well-known/ and publish it - #126
Merged
Merged
Conversation
The repository root .well-known/ was never reachable on the live site: Jekyll
excludes dotted directories, so /.well-known/security.txt returned 404 even
though the file existed in the tree.
* move .well-known/ -> www/.well-known/ (the canonical bundle location)
* add an additive overlay step between the Jekyll build and the upload so
www/.well-known/ lands at _site/.well-known/
* point the well-known enforcement workflow at the new path, keeping the
previous paths as fallbacks so nothing regresses if a file is added back
|
Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (5)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
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.
The repository root .well-known/ was never reachable on the live site: Jekyll
excludes dotted directories, so /.well-known/security.txt returned 404 even
though the file existed in the tree.
www/.well-known/ lands at _site/.well-known/
previous paths as fallbacks so nothing regresses if a file is added back
Verified before pushing: the workflow YAML parses, the overlay step sits between the build and the upload, and the overlay script was extracted from the YAML and executed against three cases — SSG produced nothing (placeholder index and
/.well-known/security.txtboth published), SSG produced a real page (not clobbered), and the Jekyll_site/wwwcase (bundle source removed). A leak check confirmsdns/and the other non-published subtrees never reach_site.Note: the estate is carrying roughly 3,200 queued Actions runs from earlier mass pushes, so this will not deploy immediately. That is a queue backlog, not a failure of this change.