Repository navigation
Point every install page at the Quickstart's tag table; unique anchors - #419
Merged
Merged
Conversation
Step 1 gets a table - 7.50 and newer, 7.02 to 7.4x, ABAP Cloud - with what to pull for each and how a tag is chosen in abapGit, and says that the release GitHub marks Latest is only the one published last: the -702 build of a version is published after the version itself. The sample count leaves the prose (the catalogue counts itself), the tutorial has twelve steps, not ten. /docs/get_started/ answers with the Quickstart instead of a 404, and the site publishes a sitemap. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014YZFmFUSt4hnK572fuJp8R
The downporting, installation, S/4 Public Cloud, transport, versioning and About pages said 'pull the 702 branch' or 'pull a release' without which one; they name the tag (X.Y.Z or X.Y.Z-702) and link the table. The runbook link in Sizing used an anchor VitePress never generates. The CAP section of Agents repeated three headings of the add-on section and got anchors with -1 suffixes; they say CAP now. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014YZFmFUSt4hnK572fuJp8R
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.
This follows up #418, which added a table to the Quickstart saying which tag to pull for which system.
702branch" or "pull a release" without saying which one. They now name the tag (X.Y.Z, orX.Y.Z-702below 7.50) and link the table. Downporting also says why a tag beats the branch: the702branch is force-pushed on every rebuild.#the-draft-table-z2ui5_t_01, an anchor VitePress never generates. It now uses-z2ui5-t-01.-1suffixes. They now say CAP.Line-length, vocabulary, audience, spelling and cross-site gates are green, and so are the 180 node tests and
docs:build.Generated by Claude Code