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

Dependencies updated #87

Merged
merged 2 commits into from
Jan 25, 2024
Merged

Dependencies updated #87

merged 2 commits into from
Jan 25, 2024

Conversation

maehr
Copy link
Owner

@maehr maehr commented Jan 23, 2024

Pull Request

Add / Remove / Change {entry name} in src/lib/data/entries.json.

Short pitch

Describe why this change is made. Alternatively, refer to existing issues if any. You could try to answer:

  • Why do you find this resource awesome?
  • How do you use this resource in your workflow?
  • What advantages / disadvantages does it have compared to {another resource}?

Checklist

Please ensure that you have completed the following tasks:

  • I have read and understood the contribution guidelines.
  • I have run npm run prepare to sort the entries in src/lib/data/entries.json alphabetically and to generate the README.md file.
  • I have run npm run format to format the repository code.
  • I have run npm run awesome-lint to ensure that the README.md file is formatted correctly.

Criteria for accepting a pull request

Contributors, please ensure that:

Maintainers, please ensure that:

  • The above criteria are followed.
  • The tests pass on the CI.
  • In the case of addition or removal, make an assessment of the awesomeness of the entry.

Updating your PR

If the maintainers notice anything that needs to be changed, they will ask you to edit your PR before merging it. Please do not open a new PR, just edit the existing one. If you're not sure how to do that, here is a guide on the different ways you can update your PR.

Appendix: running lint tests

To run tests locally using Node.js, you need to install the dependencies first:

npm install
npm run prepare

Copy link
Contributor

coderabbitai bot commented Jan 23, 2024

Warning

Rate Limit Exceeded

@maehr has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 26 minutes and 44 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.
Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.
Please see our FAQ for further information.

Commits Files that changed from the base of the PR and between f8497f4 and 570eecf.

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-tests for this file.
  • 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 tests 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 from git and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit tests.
    • @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.
  • The JSON schema for the configuration file is available here.
  • 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

Copy link

Deploying with  Cloudflare Pages  Cloudflare Pages

Latest commit: 570eecf
Status: ✅  Deploy successful!
Preview URL: https://e40117af.awesome-digital-history.pages.dev
Branch Preview URL: https://chore.awesome-digital-history.pages.dev

View logs

@maehr maehr requested a review from koilebeit January 23, 2024 12:54
@maehr maehr merged commit 2ecc3a8 into main Jan 25, 2024
5 checks passed
@maehr maehr deleted the chore branch January 25, 2024 21:21
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