docs(port): restore missing bare-metal nested-tab content (3 guides, hand-port)#76
Merged
Merged
Conversation
…hand-port) Three guides whose source-PR diffs landed inside legacy `>>` nested-tab content that the /legacy-batch-port skill couldn't apply because new-docs already had them as <Tabs><Tab> JSX. Hand-ported per /legacy-pr-port conventions: - lacp-enable-netplan (PR #9281): drop the now-incorrect "main private MAC is the lowest value" sub-paragraph from the :::info callout. - network-ipv6 (PR #9282): add "Step 4: Disable randomized IPv6 interface identifiers" inside the Windows Server 2019+ tab. Adds 2 PNGs. - vrack-configuring-on-dedicated-server (PR #9256): add CP-NAV block, consolidate the redundant "open Network menu" step in Step 2, prefix 4 nmcli commands with sudo (Fedora/NetworkManager tab). Closes the bare-metal port stream begun with PR #67 (surgical) and PR #74 (re-migrate). All 7 locales touched per guide. No regression vs develop. Original-URL: ovh/docs#9281 Original-URL: ovh/docs#9282 Original-URL: ovh/docs#9256
Y0Coss
added
the
Bare Metal
The /legacy-batch-port run that produced PR #74 stripped the legacy <style> block from every locale of ola-enable-debian9 except PT — the PT file still carries CSS rules wrapped in <style>...</style>. MDX 2 treats <style> as a JSX element and parses any {…} inside as JSX expressions. The CSS declarations (color:rgb(...), padding-right:1ch etc.) are not valid JavaScript expressions, so the acorn JSX expression parser fails and CI build:pt aborts with: MDX compile error: Could not parse expression with acorn Dropping the block aligns PT with the other six locales (none of which have a <style> block in this guide) and unblocks the CI build for the `port/new-docs-bare-metal-deferred-tabs` PR. Original-bug: PR #74 (port/new-docs-bare-metal-remigrate)
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.
Three guides whose source-PR diffs landed inside legacy
>>nested-tab content that the /legacy-batch-port skill couldn't apply because new-docs already had them as JSX. Hand-ported per /legacy-pr-port conventions:Closes the bare-metal port stream begun with PR #67 (surgical) and PR #74 (re-migrate). All 7 locales touched per guide. No regression vs develop.
Original-URL: ovh/docs#9281
Original-URL: ovh/docs#9282
Original-URL: ovh/docs#9256