Repository navigation
Redact local paths and guard Pages deploys to master - #96
Merged
luinbytes merged 2 commits intoNov 14, 2026
Merged
Conversation
luinbytes
marked this pull request as ready for review
November 14, 2026 00:29
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
[REDACTED]cells.refs/heads/mastercondition to the Pages deployment job so a manual dispatch from another branch cannot deploy.The workflow condition is a guard against accidental/non-master manual deployments, not a security boundary against someone with repository write access who can change the workflow. Stronger enforcement would require GitHub Pages/environment branch restrictions; this PR does not change those settings.
Verification
/Users/or Windows user-path strings remain, the decision row is fully redacted, and the guard appears once under the deploy job.