Repository navigation
Conversation
Contributor
File size check0 over a hard cap (fails), 10 warning(s).
Split the file, wrap the line, shorten or exempt the comment, or list the path in 5 managed file(s) skipped; repo-platform owns them. |
Vivswan
force-pushed
the
refactor/discovery-picomatch
branch
from
October 5, 2026 10:58
fbdb52e to
474dc3b
Compare
The guide sat at 1298 lines, two under the fleet's 1300-line cap on a markdown file, so the next break section could not land. Every numbered section moves verbatim to one of eight area pages under docs/upgrading/v2-to-v3/, keeping its number, title, and anchor; the index page keeps the intro, the summary table grouped by area, and the order of operations. Links that now cross pages gain their page. Two corrections ride along because the index is rewritten: the intro count reads sixty-one, and the summary table gains the row for section 61, which the base commit added without one. The one test that read the guide by path now reads the page that holds section 2.
…robe cap The two paragraphs the docs probe flagged (110 and 263 words) become five bullets with bold lead-ins, and a grammar table with the two output lines quoted in text fences. Every fact is kept; the probe reports all nine pages clean.
Vivswan
force-pushed
the
docs/upgrading-split
branch
from
October 5, 2026 10:58
42aa694 to
1daad26
Compare
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.
What this changes
One summary row, before and after:
How
../link gains a level.docs/recursively, so one path change covers the new pages.Proof
##headings 62 -> 70.Technical details
test/docs/guides.test.ts, thereadFileSyncpath in the wrapper-key fence assertion, repointed todocs/upgrading/v2-to-v3/settings-file.md.textfences; every fact kept.##headings added; the 62 old ones are kept with their text.../../links resolve (the anchor test).title, since two carry a colon.docs/upgrading/v2-to-v3.md+98 -1254; the eight pages +1302 -0;test/docs/guides.test.ts+1 -1.docs/upgrading/v2-to-v3.md,docs/upgrading/v2-to-v3/{run,settings-file,layering,sections,refusals-repository,refusals-lists,library,releases}.md,test/docs/guides.test.ts.refactor/discovery-picomatch, the branch of the PR that adds section 61.