Skip to content

docs: standardize warning syntax to GFM alert format#3115

Merged
justin808 merged 1 commit intomainfrom
jg/3114-gfm-warning-syntax
Apr 12, 2026
Merged

docs: standardize warning syntax to GFM alert format#3115
justin808 merged 1 commit intomainfrom
jg/3114-gfm-warning-syntax

Conversation

@justin808
Copy link
Copy Markdown
Member

@justin808 justin808 commented Apr 12, 2026

Summary

  • Converts 3 remaining > **Warning:** instances to > [!WARNING] GFM alert syntax for consistency with the 30+ GFM alerts already used across docs

Files updated

  • docs/oss/building-features/testing-configuration.md
  • docs/oss/deployment/docker-deployment.md
  • docs/oss/migrating/rsc-troubleshooting.md

Closes #3114

Test plan

  • Verify rendered warnings display correctly on GitHub

🤖 Generated with Claude Code


Note

Low Risk
Low risk: documentation-only formatting changes with no code or behavior impact.

Overview
Updates docs to replace remaining > **Warning:** blockquotes with GitHub alert callouts (> [!WARNING]) for consistent rendering across the guides, including testing configuration, Kubernetes migration guidance, and RSC troubleshooting.

Reviewed by Cursor Bugbot for commit 96c2ae5. Bugbot is set up for automated code reviews on this repo. Configure here.

Summary by CodeRabbit

  • Documentation
    • Updated warning callout formatting across testing configuration, Docker deployment, and Kubernetes migration guidance documentation to use admonition-style warnings for improved consistency and readability.

Convert 3 remaining `> **Warning:**` instances to `> [!WARNING]`
for consistency with the 30+ GFM alerts already used across docs.

Closes #3114

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Apr 12, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: bb758ac0-f0a9-4b2f-89bb-d084fcb2a03e

📥 Commits

Reviewing files that changed from the base of the PR and between 6a18c16 and 96c2ae5.

📒 Files selected for processing (3)
  • docs/oss/building-features/testing-configuration.md
  • docs/oss/deployment/docker-deployment.md
  • docs/oss/migrating/rsc-troubleshooting.md

Walkthrough

Three documentation files are updated to standardize warning syntax from bold-style (> **Warning:**) to GitHub Flavored Markdown (GFM) alert format (> [!WARNING]) for consistency across the documentation.

Changes

Cohort / File(s) Summary
Warning syntax standardization
docs/oss/building-features/testing-configuration.md, docs/oss/deployment/docker-deployment.md, docs/oss/migrating/rsc-troubleshooting.md
Converted legacy bold-style warnings (> **Warning:**) to GFM alert format (> [!WARNING]) for consistent documentation styling. Content and meaning preserved.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 With whiskers twitching, we hopped with glee,
Standardizing warnings for all to see!
From bold to bright alerts, the syntax is new,
Consistency springing in all that we do! ✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'docs: standardize warning syntax to GFM alert format' directly summarizes the main change: converting warning syntax across three documentation files from bold-style to GFM alert format.
Linked Issues check ✅ Passed All three required files have been updated with GFM alert syntax conversions as specified in issue #3114: testing-configuration.md, docker-deployment.md, and rsc-troubleshooting.md.
Out of Scope Changes check ✅ Passed All changes are within scope—only documentation warning syntax conversions were made; no unrelated modifications to other files or content were introduced.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch jg/3114-gfm-warning-syntax

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@claude
Copy link
Copy Markdown
Contributor

claude Bot commented Apr 12, 2026

The three conversions look correct and consistent with the GFM alert format used elsewhere in the docs.

One instance was missed though — docs/oss/migrating/rsc-preparing-app.md line 485 still uses the old > **Warning:** syntax:

> **Warning: Compression middleware.** If your app uses `Rack::Deflater`, ...

Should be converted to:

> [!WARNING]
> **Compression middleware.** If your app uses `Rack::Deflater`, ...

Once that's addressed, the docs will be fully consistent.

@greptile-apps
Copy link
Copy Markdown

greptile-apps Bot commented Apr 12, 2026

Greptile Summary

Standardizes the last 3 remaining > **Warning:** blockquotes to > [!WARNING] GitHub Flavored Markdown alert syntax, matching the format already used by 30+ other alerts in the docs. All content is preserved verbatim; no logic or code is affected.

Confidence Score: 5/5

Safe to merge — documentation-only formatting change with no logic impact.

All three changes are mechanical format conversions with no content modifications. The GFM alert syntax is correct in each file, including the indented blockquote inside a list item in docker-deployment.md. No code, configuration, or logic is touched.

No files require special attention.

Important Files Changed

Filename Overview
docs/oss/building-features/testing-configuration.md Converts one > **Warning:** to > [!WARNING] GFM alert format; content unchanged.
docs/oss/deployment/docker-deployment.md Converts one indented > **Warning:** (inside a list item) to > [!WARNING]; indentation preserved correctly.
docs/oss/migrating/rsc-troubleshooting.md Converts one > **Warning:** to > [!WARNING] GFM alert format; content unchanged.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["Old format\n> **Warning:** message"] -->|"Converted in 3 files"| B["New format\n> [!WARNING]\n> message"]
    B --> C["Consistent with 30+ existing\nGFM alerts across docs"]
Loading

Reviews (1): Last reviewed commit: "docs: standardize warning syntax to GFM ..." | Re-trigger Greptile

@justin808 justin808 merged commit 45ac79d into main Apr 12, 2026
10 of 11 checks passed
@justin808 justin808 deleted the jg/3114-gfm-warning-syntax branch April 12, 2026 18:34
justin808 added a commit that referenced this pull request Apr 12, 2026
## Summary

- Converts 3 remaining `> **Warning:**` instances to `> [!WARNING]` GFM
alert syntax for consistency with the 30+ GFM alerts already used across
docs

### Files updated
- `docs/oss/building-features/testing-configuration.md`
- `docs/oss/deployment/docker-deployment.md`
- `docs/oss/migrating/rsc-troubleshooting.md`

Closes #3114

## Test plan

- [ ] Verify rendered warnings display correctly on GitHub

🤖 Generated with [Claude Code](https://claude.com/claude-code)

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Low Risk**
> Low risk: documentation-only formatting changes with no code or
behavior impact.
> 
> **Overview**
> Updates docs to replace remaining `> **Warning:**` blockquotes with
GitHub alert callouts (`> [!WARNING]`) for consistent rendering across
the guides, including testing configuration, Kubernetes migration
guidance, and RSC troubleshooting.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
96c2ae5. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Documentation**
* Updated warning callout formatting across testing configuration,
Docker deployment, and Kubernetes migration guidance documentation to
use admonition-style warnings for improved consistency and readability.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Co-authored-by: Claude Opus 4.6 (1M context) <[email protected]>
justin808 added a commit that referenced this pull request Apr 12, 2026
## Summary

- Converts 3 remaining `> **Warning:**` instances to `> [!WARNING]` GFM
alert syntax for consistency with the 30+ GFM alerts already used across
docs

### Files updated
- `docs/oss/building-features/testing-configuration.md`
- `docs/oss/deployment/docker-deployment.md`
- `docs/oss/migrating/rsc-troubleshooting.md`

Closes #3114

## Test plan

- [ ] Verify rendered warnings display correctly on GitHub

🤖 Generated with [Claude Code](https://claude.com/claude-code)

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Low Risk**
> Low risk: documentation-only formatting changes with no code or
behavior impact.
> 
> **Overview**
> Updates docs to replace remaining `> **Warning:**` blockquotes with
GitHub alert callouts (`> [!WARNING]`) for consistent rendering across
the guides, including testing configuration, Kubernetes migration
guidance, and RSC troubleshooting.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
96c2ae5. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Documentation**
* Updated warning callout formatting across testing configuration,
Docker deployment, and Kubernetes migration guidance documentation to
use admonition-style warnings for improved consistency and readability.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Co-authored-by: Claude Opus 4.6 (1M context) <[email protected]>
justin808 added a commit that referenced this pull request Apr 12, 2026
## Summary

- Converts 3 remaining `> **Warning:**` instances to `> [!WARNING]` GFM
alert syntax for consistency with the 30+ GFM alerts already used across
docs

### Files updated
- `docs/oss/building-features/testing-configuration.md`
- `docs/oss/deployment/docker-deployment.md`
- `docs/oss/migrating/rsc-troubleshooting.md`

Closes #3114

## Test plan

- [ ] Verify rendered warnings display correctly on GitHub

🤖 Generated with [Claude Code](https://claude.com/claude-code)

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Low Risk**
> Low risk: documentation-only formatting changes with no code or
behavior impact.
> 
> **Overview**
> Updates docs to replace remaining `> **Warning:**` blockquotes with
GitHub alert callouts (`> [!WARNING]`) for consistent rendering across
the guides, including testing configuration, Kubernetes migration
guidance, and RSC troubleshooting.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
96c2ae5. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Documentation**
* Updated warning callout formatting across testing configuration,
Docker deployment, and Kubernetes migration guidance documentation to
use admonition-style warnings for improved consistency and readability.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Co-authored-by: Claude Opus 4.6 (1M context) <[email protected]>
justin808 added a commit that referenced this pull request Apr 12, 2026
…ages

* origin/main: (44 commits)
  Consolidate CSP nonce sanitization into shared module (#2828)
  Add comprehensive --rsc-pro generator tests (#3098)
  fix: cross-env validation and docs for renderer password (#3090)
  Improve package metadata and Pro upgrade CTAs (#3112)
  docs: standardize warning syntax to GFM alert format (#3115)
  docs: improve react-intl documentation for React Server Components (#3085)
  Fix generator CI SSR regression on main (#3110)
  Refocus GitHub README on docs navigation (#3113)
  Add manual dev environment testing checklist for coding agents (#3074)
  Bump version to 16.6.0
  Update CHANGELOG.md for 16.6.0 (#3078)
  fix: node-renderer diagnostic improvements (#3086)
  fix: pin third-party npm deps in generator to prevent peer dep conflicts (#3083)
  chore(deps): bump lodash from 4.17.23 to 4.18.1 in the npm-security group across 1 directory (#2920)
  fix: refactor formatExceptionMessage to accept generic request context (#2877)
  Bump version to 16.6.0.rc.1
  Update CHANGELOG.md for 16.6.0.rc.1 (#3079)
  Update CHANGELOG.md unreleased section (#3077)
  Fix Content-Length mismatch and null renderingRequest errors in node renderer (#3069)
  Improve memory debugging docs with simpler heap snapshot approach (#3072)
  ...

# Conflicts:
#	docs/pro/home-pro.md
#	docs/pro/react-on-rails-pro.md
#	docs/sidebars.ts
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs: standardize warning syntax to GFM alert format

1 participant