Skip to content

docs: minor documentation formatting update#29302

Closed
thanhdatloveyou18-coder wants to merge 1 commit into
calcom:mainfrom
thanhdatloveyou18-coder:patch-1778550837
Closed

docs: minor documentation formatting update#29302
thanhdatloveyou18-coder wants to merge 1 commit into
calcom:mainfrom
thanhdatloveyou18-coder:patch-1778550837

Conversation

@thanhdatloveyou18-coder

Copy link
Copy Markdown

This PR addresses minor formatting issues and cleans up trailing whitespace to improve readability.

@github-actions

Copy link
Copy Markdown
Contributor

Welcome to Cal.diy, @thanhdatloveyou18-coder! Thanks for opening this pull request.

A few things to keep in mind:

  • This is Cal.diy, not Cal.com. Cal.diy is a community-driven, fully open-source fork of Cal.com licensed under MIT. Your changes here will be part of Cal.diy — they will not be deployed to the Cal.com production app.
  • Please review our Contributing Guidelines if you haven't already.
  • Make sure your PR title follows the Conventional Commits format.

A maintainer will review your PR soon. Thanks for contributing!

@coderabbitai

coderabbitai Bot commented May 12, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

This pull request adds a formatting-only HTML comment within the README Acknowledgements section. The change consists of three lines inserted at lines 832–834, including the comment and surrounding whitespace. No content, structure, or exported entities are modified.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title 'docs: minor documentation formatting update' accurately describes the changeset, which consists of a formatting-only update to README.md in the Acknowledgements section.
Description check ✅ Passed The description 'This PR addresses minor formatting issues and cleans up trailing whitespace to improve readability' directly relates to the changeset, which adds a formatting comment and improves documentation readability.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
README.md (1)

832-834: ⚡ Quick win

PR description doesn't match the actual changes.

The PR description claims to "remove trailing whitespace to improve readability," but these changes actually add two blank lines and an HTML comment. The comment provides no value and the extra whitespace doesn't improve readability.

✂️ Suggested removal
 - [Prisma](https://prisma.io/)
-
-
-<!-- Formatting update -->
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` around lines 832 - 834, The PR adds an HTML comment "<!--
Formatting update -->" and two blank lines in README.md but the description says
it removed trailing whitespace; remove the extra blank lines and delete the HTML
comment from README.md (or alternatively update the PR/commit message to
accurately describe the changes), then amend the commit or add a follow-up
commit so the file only contains intended whitespace fixes and the PR
description matches the actual diff.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@README.md`:
- Around line 832-834: The PR adds an HTML comment "<!-- Formatting update -->"
and two blank lines in README.md but the description says it removed trailing
whitespace; remove the extra blank lines and delete the HTML comment from
README.md (or alternatively update the PR/commit message to accurately describe
the changes), then amend the commit or add a follow-up commit so the file only
contains intended whitespace fixes and the PR description matches the actual
diff.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 102df862-f8d2-44e2-832d-74f5bc8d5db0

📥 Commits

Reviewing files that changed from the base of the PR and between fb01494 and 65c75e0.

📒 Files selected for processing (1)
  • README.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants