[Docs Preview] Bazel Docs: Fix syntax errors in 8.5.1 docs.#29211
Draft
copybara-service[bot] wants to merge 1 commit intomasterfrom
Draft
[Docs Preview] Bazel Docs: Fix syntax errors in 8.5.1 docs.#29211copybara-service[bot] wants to merge 1 commit intomasterfrom
copybara-service[bot] wants to merge 1 commit intomasterfrom
Conversation
Mostly authored by Gemini CLI:
<details>
<summary>Prompt 1</summary>
You're an experienced tech writer.
Your task is to fix all remaining syntax errors in .mdx files in the current directory.
You can find syntax errors by running "mint validate".
Rules:
- Only fix files mentioned in the output of "mint validate"
- Do not insert blank lines
- Do not change the indentation of lines
- Do not introduce trailing whitespaces
- Do not delete any of the text
- Replace `<pre>` blocks with Markdown fenced code blocks (three backticks).
- Contents of Markdown fenced code blocks cannot be on the same line as the three backticks.
- Do not merge three or more lines into a single line.
- Do not replace HTML tables with Markdown tables.
</details>
<details>
<summary>Output 1</summary>
I have addressed the majority of the syntax errors in the .mdx files by escaping special characters (like {, $, and <), fixing malformed HTML tags, and ensuring correct tag nesting (especially for <pre>, <td>,
and <a> tags). I also corrected frontmatter issues and removed stray tags. Most files now pass validation, resolving the bulk of the syntax issues identified by mint validate.
</details>
<details>
<summary>Prompt 2</summary>
Please fix the table data entries in docs/cc-toolchain-config-reference.mdx:
- If the <td> element and the text are on a single line, make sure that the matching </td> is on the same line
- If the text spans multiple lines, make sure that both <td> and </td> have their own lines, i.e. they are not on the same line as the text.
</details>
PiperOrigin-RevId: 888371664
299cb87 to
7afd64f
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.
Bazel Docs: Fix syntax errors in 8.5.1 docs.
Mostly authored by Gemini CLI:
Prompt 1
You're an experienced tech writer.
Your task is to fix all remaining syntax errors in .mdx files in the current directory.
You can find syntax errors by running "mint validate".
Rules:
<pre>blocks with Markdown fenced code blocks (three backticks).Output 1
I have addressed the majority of the syntax errors in the .mdx files by escaping special characters (like {, $, and <), fixing malformed HTML tags, and ensuring correct tag nesting (especially for
Prompt 2
Please fix the table data entries in docs/cc-toolchain-config-reference.mdx: