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 VNPay documentation and badges #11

Merged
merged 3 commits into from
May 22, 2024
Merged

Update VNPay documentation and badges #11

merged 3 commits into from
May 22, 2024

Conversation

lehuygiang28
Copy link
Owner

@lehuygiang28 lehuygiang28 commented May 22, 2024

Pull Request Description

  • Update VNPay documentation and badges

Type of Change

Please check the type of change your PR introduces:

  • Bugfix
  • New feature
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Documentation content changes
  • Other (please describe):

Does this introduce a breaking change?

  • Yes
  • No

If yes, please describe the impact and migration path for existing applications:

Related Issues or References

Please list any related issues or references here:

Summary by CodeRabbit

  • Documentation
    • Renamed project from "VNPay" to "VNPay Lib" in README files.
    • Updated badge URLs and images in README files.
    • Changed "Buy Me A Coffee" image in README file.
    • Added SEO metadata and social card details in documentation config.
    • Set default language for code snippets to TypeScript.
    • Introduced an announcement bar for contributors.

Copy link

vercel bot commented May 22, 2024

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

Name Status Preview Comments Updated (UTC)
vnpay ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 22, 2024 3:50pm

Copy link

coderabbitai bot commented May 22, 2024

Walkthrough

The recent updates primarily focus on rebranding the project from "vnpay" to "VNPay Lib" across various documentation files. This includes updating README files with new project names, badge URLs, and images. Additionally, the Docusaurus configuration has been enhanced with improved SEO metadata, social card details, and a new announcement bar for contributors. These changes aim to provide a more polished and informative presentation of the project.

Changes

File Change Summary
README.md Renamed project to "VNPay Lib", updated badge URLs, and changed "Buy Me A Coffee" image source.
README_en-US.md Renamed project to "VNPay Lib", updated badge images and links for NPM version, license, and downloads.
docs/docusaurus.config.ts Added SEO metadata, updated social card details, set default Prism language, and added an announcement bar.

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: 4

Outside diff range and nitpick comments (4)
README_en-US.md (2)

Line range hint 48-48: Correct heading levels to maintain a logical structure.

- #### Initialize
+ ### Initialize
- #### `VNPay` is an open-source and free project. If you find it useful, please consider supporting it by starring ⭐️ the repository on [Github](https://github.com/lehuygiang28/vnpay) and buying me a coffee.
+ ### `VNPay` is an open-source and free project. If you find it useful, please consider supporting it by starring ⭐️ the repository on [Github](https://github.com/lehuygiang28/vnpay) and buying me a coffee.

Line range hint 31-31: Consider removing the dollar signs in command examples for consistency, unless showing command output.

- $ npm install vnpay
+ npm install vnpay
- $ yarn add vnpay
+ yarn add vnpay
- $ pnpm add vnpay
+ pnpm add vnpay
README.md (2)

Line range hint 48-48: Correct heading levels to maintain a logical structure.

- #### Khởi tạo
+ ### Khởi tạo
- #### Thư viện VNPay là một dự án mã nguồn mở và miễn phí. Nếu bạn thấy nó hữu ích, hãy xem xét hỗ trợ bằng cách tặng một ⭐️ trên [GitHub](https://github.com/lehuygiang28/vnpay) và mua tác giả một cốc cà phê.
+ ### Thư viện VNPay là một dự án mã nguồn mở và miễn phí. Nếu bạn thấy nó hữu ích, hãy xem xét hỗ trợ bằng cách tặng một ⭐️ trên [GitHub](https://github.com/lehuygiang28/vnpay) và mua tác giả một cốc cà phê.

Line range hint 31-31: Consider removing the dollar signs in command examples for consistency, unless showing command output.

- $ npm install vnpay
+ npm install vnpay
- $ yarn add vnpay
+ yarn add vnpay
- $ pnpm add vnpay
+ pnpm add vnpay
Review Details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE

Commits Files that changed from the base of the PR and between 67f6188 and e0d3f6e.
Files selected for processing (3)
  • README.md (3 hunks)
  • README_en-US.md (3 hunks)
  • docs/docusaurus.config.ts (4 hunks)
Files skipped from review due to trivial changes (1)
  • docs/docusaurus.config.ts
Additional Context Used
Markdownlint (12)
README.md (6)

48: Expected: h3; Actual: h4
Heading levels should only increment by one level at a time


64: Expected: h3; Actual: h4
Heading levels should only increment by one level at a time


31: null
Dollar signs used before commands without showing output


37: null
Dollar signs used before commands without showing output


43: null
Dollar signs used before commands without showing output


77: null
Images should have alternate text (alt text)

README_en-US.md (6)

48: Expected: h3; Actual: h4
Heading levels should only increment by one level at a time


64: Expected: h3; Actual: h4
Heading levels should only increment by one level at a time


31: null
Dollar signs used before commands without showing output


37: null
Dollar signs used before commands without showing output


43: null
Dollar signs used before commands without showing output


77: null
Images should have alternate text (alt text)

Path-based Instructions (2)
README_en-US.md (1)

Pattern **/*.md: Review the Markdown files to ensure they are well-structured follow Docusaurus's best practices, easy to read, and contain accurate and up-to-date information. Check for proper formatting, grammar, and spelling. Ensure that the content is relevant and engaging for the target audience. Highlight any inconsistencies or errors and suggest improvements to enhance the overall quality of the documentation.

README.md (1)

Pattern **/*.md: Review the Markdown files to ensure they are well-structured follow Docusaurus's best practices, easy to read, and contain accurate and up-to-date information. Check for proper formatting, grammar, and spelling. Ensure that the content is relevant and engaging for the target audience. Highlight any inconsistencies or errors and suggest improvements to enhance the overall quality of the documentation.

Additional comments not posted (2)
README_en-US.md (1)

1-1: Update to project title aligns with rebranding efforts.

README.md (1)

1-1: Update to project title aligns with rebranding efforts.

README_en-US.md Show resolved Hide resolved
README_en-US.md Show resolved Hide resolved
README.md Show resolved Hide resolved
README.md Show resolved Hide resolved
@lehuygiang28 lehuygiang28 self-assigned this May 22, 2024
@lehuygiang28 lehuygiang28 merged commit 876ace2 into main May 22, 2024
6 checks passed
@lehuygiang28 lehuygiang28 deleted the update_docs branch May 26, 2024 07:55
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.

1 participant