fix(docs): delete 5 workspace-only symlinks (correct fix for #59, which didn't work)#60
Merged
Merged
Conversation
The pages build has failed on every main push for 5+ days (9 consecutive failures since 2026-06-01). Root cause: 5 symlinks in docs/ point to sibling workspace directories that don't exist on the CI runner: docs/HARNESS.md -> ../../docs/HARNESS.md docs/HARNESS_BACKLOG.md -> ../../docs/HARNESS_BACKLOG.md docs/FEATURE_INTAKE.md -> ../../docs/FEATURE_INTAKE.md docs/evidence/README.md -> ../../../docs/evidence/README.md docs/templates/story.md -> ../../../docs/templates/story.md Jekyll's `entry_filter.rb:symlink_outside_site_source?` check fires during directory scan, before any `exclude:` filter runs, so `_config.yml` excludes cannot rescue it (verified — PR #59 added a _config.yml exclude rule, Pages build still failed identically). The symlinks were intentionally added in commit d39c598 ('docs: wire harness via workspace symlinks') to wire Sisyphus harness scaffolding from /Users/nhonh/Documents/personal/docs/ on local dev. The local dev workflow can be re-established by re-creating the symlinks locally (they don't need to be tracked — workspace tooling, not repo content). Also removes docs/_config.yml (added in PR #59, now dead config: its exclude list references files that will no longer exist). Verified locally: 0 HARNESS/HARNESS_BACKLOG/FEATURE_INTAKE references in repo source code (`git grep` confirmed). They were docs-only artifacts, no code path depends on them.
There was a problem hiding this comment.
Code Review
This pull request removes several workspace-only symlinks pointing to external documentation files, including FEATURE_INTAKE.md, HARNESS.md, and HARNESS_BACKLOG.md, as well as their corresponding exclusion rules in the configuration file. These changes clean up the repository structure. There are no review comments, and I have no additional feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
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.
Context
The
pages build and deploymentworkflow has failed on every main push for 5+ days (9 consecutive failures). PR #59 attempted to fix this with a Jekyll_config.ymlexclude rule — that approach did not work, and this PR is the corrected fix.Why PR #59 failed
The Jekyll
symlink_outside_site_source?check fires inentry_filter.rbduring directory scan, before anyexclude:filter runs. Trace from run 27066018295 (post-#59 merge):The exclude list is consulted later in
reader.rb:117 filter_entries, but the scan has already crashed on the symlink._config.ymlexclude rules cannot rescue symlinks that point outside the site source.Why these symlinks exist at all
They were intentionally added in commit
d39c598 docs: wire harness via workspace symlinksto wire Sisyphus harness scaffolding from/Users/nhonh/Documents/personal/docs/on the local dev machine. Resolves fine locally, but the symlink targets don't exist on the CI runner (which has only the cloned repo, not the workspace).Fix
Delete the 5 symlinks + the now-dead
_config.yml(which had a stale exclude list). The local dev workspace wiring can be re-established by re-creating the symlinks locally — they don't need to be tracked (workspace tooling, not repo content).Files deleted (6 total)
docs/HARNESS.mddocs/HARNESS_BACKLOG.mddocs/FEATURE_INTAKE.mddocs/evidence/README.mddocs/templates/story.mddocs/_config.ymlVerification (post-merge)
Expected: the next
pushto main will triggerpages build and deploymentwithconclusion: success. The Pages site (https://hoainho.github.io/react-debugger-extension/) will be live.HARNESS.local.md(the only real harness file in docs/) is preserved.Also verified via
git grep: zero references toHARNESS.md,HARNESS_BACKLOG.md, orFEATURE_INTAKE.mdanywhere in the repo source code. They were docs-only artifacts.Risk
Tiny. Pure deletion, no code logic affected. If the user wants the local workspace wiring back, the 5
ln -scommands are a one-liner per file.Related