Skip to content

docs: update README.md to fix grammer #124

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 15, 2025
Merged

Conversation

shenxianpeng
Copy link
Contributor

@shenxianpeng shenxianpeng commented Jul 15, 2025

Summary by CodeRabbit

  • Documentation
    • Improved readability and clarity in the documentation by correcting capitalization, grammar, and phrasing.
    • Enhanced punctuation and overall text quality in the README.
    • Updated example workflow configuration to reflect a change in default boolean input value.

@shenxianpeng shenxianpeng requested a review from a team as a code owner July 15, 2025 08:50
@shenxianpeng shenxianpeng added the documentation Improvements or additions to documentation label Jul 15, 2025
Copy link

coderabbitai bot commented Jul 15, 2025

Caution

Review failed

The pull request is closed.

Walkthrough

The README.md file was updated with textual and stylistic improvements. These changes include corrections to capitalization, grammar, punctuation, and phrasing for better clarity and readability. Additionally, the default value of the imperative input in the example workflow was changed from true to false. No code, configuration, or functionality was altered.

Changes

File(s) Change Summary
README.md Corrected capitalization, grammar, punctuation, and phrasing; updated default value of imperative input from true to false in example workflow.

Possibly related PRs

Poem

A hop and a skip through README land,
Where commas and capitals now proudly stand.
Imperative’s default takes a gentle fall,
Now false by default, to clarify all.
The docs shine bright, a clearer view,
For every coder hopping through! 🐇✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5688e3d and 8f8d1ef.

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

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

Commit-Check ✔️

@shenxianpeng shenxianpeng changed the title docs: update README.md to fix gramer docs: update README.md to fix grammer Jul 15, 2025
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

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

36-36: Tighten wording on the permissions inline-comment

A minor grammar tweak makes the note flow better.

-    permissions:  # use permissions because use of pr-comments
+    permissions:  # explicitly set permissions because PR comments require them

115-117: Optional wording polish

Reads a little smoother with “it” moved forward.

-> `merge-base` is an experimental feature. By default, it's disabled.
+> `merge-base` is an experimental feature. It's disabled by default.

124-127: List style & clarity for dry-run description

-* **Description**: run checks without failing. exit code is 0; otherwise is 1.
+* **Description**: run checks without failing. Exit code is always `0`; otherwise `1`.

139-139: Minor wording tweak in the pr-comments note

-> `pr-comments` is an experimental feature. By default, it's disabled. To use it, you need to set `GITHUB_TOKEN` in the GitHub Action.
+> `pr-comments` is an experimental feature and is disabled by default. Enable it by setting `GITHUB_TOKEN` in the workflow.

143-144: Rephrase the “default rule” sentence for readability

-Note: the default rule of above inputs is following [this configuration](https://github.com/commit-check/commit-check/blob/main/.commit-check.yml). If you want to customize, just add your `.commit-check.yml` config file under your repository root directory.
+Note: The default behaviour of the inputs above follows [this configuration](https://github.com/commit-check/commit-check/blob/main/.commit-check.yml). To customise it, add a `.commit-check.yml` file to your repository root.

194-194: Tighten feedback sentence

-To provide feedback (requesting a feature or reporting a bug), please post to [issues](https://github.com/commit-check/commit-check/issues).
+To request a feature or report a bug, please open an [issue](https://github.com/commit-check/commit-check/issues).
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 38641d6 and 5688e3d.

📒 Files selected for processing (1)
  • README.md (8 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
README.md

84-84: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


85-85: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


89-89: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


90-90: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


110-110: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


111-111: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


125-125: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)

🔇 Additional comments (1)
README.md (1)

54-54: Change looks good

No further issues spotted with the imperative flag line.

Comment on lines 83 to 92
- **Description**: check commit message formatting convention.
- By default the rule follows [conventional commits](https://www.conventionalcommits.org/).
- By default, the rule follows [conventional commits](https://www.conventionalcommits.org/).
- Default: `true`

### `branch`

- **Description**: check git branch naming convention.
- By default the rule follows [conventional branch](https://conventional-branch.github.io/).
- By default, the rule follows [conventional branch](https://conventional-branch.github.io/).
- Default: `true`

Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Unify list-marker style to satisfy markdown-lint

markdownlint flags these lines for using - while the rest of the doc uses *.
Switching keeps the style consistent and silences MD004.

-  - By default, the rule follows [conventional commits](https://www.conventionalcommits.org/).
+  * By default, the rule follows [conventional commits](https://www.conventionalcommits.org/).-  - By default, the rule follows [conventional branch](https://conventional-branch.github.io/).
+  * By default, the rule follows [conventional branch](https://conventional-branch.github.io/).
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- **Description**: check commit message formatting convention.
- By default the rule follows [conventional commits](https://www.conventionalcommits.org/).
- By default, the rule follows [conventional commits](https://www.conventionalcommits.org/).
- Default: `true`
### `branch`
- **Description**: check git branch naming convention.
- By default the rule follows [conventional branch](https://conventional-branch.github.io/).
- By default, the rule follows [conventional branch](https://conventional-branch.github.io/).
- Default: `true`
- **Description**: check commit message formatting convention.
* By default, the rule follows [conventional commits](https://www.conventionalcommits.org/).
- Default: `true`
### `branch`
- **Description**: check git branch naming convention.
* By default, the rule follows [conventional branch](https://conventional-branch.github.io/).
- Default: `true`
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

83-83: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


84-84: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


85-85: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


89-89: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


90-90: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


91-91: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)

🤖 Prompt for AI Agents
In README.md around lines 83 to 92, the list markers use '-' while the rest of
the document uses '*', causing markdownlint MD004 warnings. Change all '-' list
markers in this section to '*' to unify the list-marker style and maintain
consistency throughout the document.

Comment on lines 108 to 112
### `merge-base`

- **Description**: check current branch is rebased onto target branch.
- **Description**: check current branch is rebased onto the target branch.
- Default: `false`

Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Fix MD004 and capitalisation in the merge-base description

-* **Description**: check current branch is rebased onto the target branch.
+* **Description**: check that the current branch is rebased onto the target branch.

Also swaps - for * to keep list-marker style consistent.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
### `merge-base`
- **Description**: check current branch is rebased onto target branch.
- **Description**: check current branch is rebased onto the target branch.
- Default: `false`
### `merge-base`
* **Description**: check that the current branch is rebased onto the target branch.
- Default: `false`
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

110-110: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


111-111: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)

🤖 Prompt for AI Agents
In README.md around lines 108 to 112, fix the markdown linting issue MD004 by
ensuring consistent list marker style by replacing the dash (-) with an asterisk
(*). Also, capitalize the first letter of the description for `merge-base` to
maintain proper sentence case. Update the list item to start with "*
Description: Check current branch is rebased onto the target branch." and keep
the rest of the formatting consistent.

@shenxianpeng shenxianpeng merged commit e6d7e53 into main Jul 15, 2025
2 checks passed
@shenxianpeng shenxianpeng deleted the shenxianpeng-patch-1 branch July 15, 2025 08:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant