fix(batch-changes): repair broken permissions table#1770
Open
eugenio-sanchez-sg wants to merge 1 commit intomainfrom
Open
fix(batch-changes): repair broken permissions table#1770eugenio-sanchez-sg wants to merge 1 commit intomainfrom
eugenio-sanchez-sg wants to merge 1 commit intomainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
enriquegh
approved these changes
May 8, 2026
Contributor
enriquegh
left a comment
There was a problem hiding this comment.
Nice! LGTM via the preview deployment
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
Fixes the broken table under "Batch Change access for each permission level" on
/batch-changes/permissions-in-batch-changes. Previously the table rendered as asingle paragraph with literal
|separators visible to the reader.Currently at Permissions in Batch Changes
You can see the page here
After (locally)
Why
The markdown was malformed in two ways:
|---|separator row.GFM requires the separator to be on the line immediately after the header,
otherwise the whole block falls back to a paragraph.
|pipes, unlike every other table inthe repo.
How
Rewrote the table using the standard pipe-delimited form already used elsewhere
in the docs (e.g.,
docs/tutorials/index.mdx). No content changes — the actionsand ✅/❌ values are identical to the previous source.
Test plan
pnpm run devand visit/batch-changes/permissions-in-batch-changesas a real table with three columns (Batch change action / Read / Admin)