Skip to content
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

Update README.md #32

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update README.md #32

wants to merge 1 commit into from

Conversation

hoichoidev
Copy link
Collaborator

@hoichoidev hoichoidev commented May 9, 2024

Summary by CodeRabbit

  • Documentation
    • Updated the formatting in the README file, specifically in the contributing guidelines section for better clarity.

Signed-off-by: hoichoi.tech <87117724+hoichoidev@users.noreply.github.com>
Copy link

vercel bot commented May 9, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
imageresizer ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 9, 2024 0:19am

Copy link

coderabbitai bot commented May 9, 2024

Walkthrough

The recent update focuses primarily on enhancing the readability of the README file, specifically within the contributing guidelines section. The modification involves reformatting by shifting the section title to a separate line, ensuring clarity and better visual organization. No changes were made to the declarations of exported or public entities in the codebase.

Changes

File Change Summary
README.md Updated formatting of the contributing guidelines section title to a new line.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

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>.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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

@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: 3

Out of diff range and nitpick comments (2)
README.md (2)

Line range hint 72-72: Improve the wording for better clarity.

- Have an idea to make this project better? Share it with us by opening a new issue...
+ If you have ideas for improving this project, please share them by opening a new issue...

Line range hint 78-89: Remove trailing spaces and extra blank lines for cleaner formatting.

- 78: Expected: 0 or 2; Actual: 1
- 79: Expected: 0 or 2; Actual: 1
- 81: Expected: 0 or 2; Actual: 1
- 82: Expected: 0 or 2; Actual: 1
- 17: Expected: 1; Actual: 2
- 64: Expected: 1; Actual: 2
- 89: Expected: 1; Actual: 2
+ 78: Expected: 0 or 2; Actual: 0
+ 79: Expected: 0 or 2; Actual: 0
+ 81: Expected: 0 or 2; Actual: 0
+ 82: Expected: 0 or 2; Actual: 0
+ 17: Expected: 1; Actual: 1
+ 64: Expected: 1; Actual: 1
+ 89: Expected: 1; Actual: 1
Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits Files that changed from the base of the PR and between fb5eb36 and fe84ae5.
Files selected for processing (1)
  • README.md (1 hunks)
Additional Context Used
LanguageTool (4)
README.md (4)

Near line 72: The wording of this phrase can be improved.
Context: ...gesting enhancements**: Have an idea to make this project better? Share it with us by opening a new issu...


Near line 73: Using many exclamation marks might seem excessive (in this case: 12 exclamation marks for a text that’s 3060 characters long)
Context: ...Want to submit a fix or a feature? Great! Fork the repository, make your changes,...


Near line 83: Possible missing preposition found.
Context: ...l Request' button to send your changes review. ## Please see our [CONTRIBUTING.md](C...


Near line 86: This sentence should probably be started with a verb instead of the noun ‘Checkout’. If not, consider inserting a comma for better clarity.
Context: ... on how to contribute to this project. Checkout the current [issues](https://github.com...

README.md Show resolved Hide resolved
@@ -82,7 +82,7 @@ Here are some ways you can contribute:
6. **Push to the branch**:
7. **Submit a pull request**: Go to your fork on GitHub and click the 'Pull Request' button to send your changes review.
Copy link

Choose a reason for hiding this comment

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

Insert the missing preposition for grammatical correctness.

- ...to send your changes  review.
+ ...to send your changes for review.

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.

Suggested change
7. **Submit a pull request**: Go to your fork on GitHub and click the 'Pull Request' button to send your changes review.
7. **Submit a pull request**: Go to your fork on GitHub and click the 'Pull Request' button to send your changes for review.

README.md Show resolved Hide resolved
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.

2 participants