jsonresume / jsonresume.org

The mono repo that builds the homepage, utils, ui components, registry and anything else
https://jsonresume.org
81 stars 22 forks source link

remove part of the "global install crap" #14

Closed levino closed 11 months ago

levino commented 11 months ago

also updates the README with the new usage

vercel[bot] commented 11 months ago

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

Name Status Preview Comments Updated (UTC)
jsonresume-org-homepage ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 23, 2023 5:51pm
jsonresume-org-registry ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 23, 2023 5:51pm
coderabbitai[bot] commented 11 months ago

[!WARNING]

Rate Limit Exceeded

@levino has exceeded the limit for the number of files or commits that can be reviewed per hour. Please wait 1 minutes and 24 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. 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](https://coderabbit.ai/docs/faq) for further information.
Commits Files that changed from the base of the PR and between a5ef157134568beac20d57a5811e70307318daf9 and e1fbbf7aa70a061fd15f42381c03de724b1c683f.

Tips ### Chat with CodeRabbit Bot (`@coderabbitai`) - If you reply to a *review comment* from CodeRabbit, the bot will automatically respond. - To engage with CodeRabbit bot directly around the specific lines of code in the PR, mention @coderabbitai in your review comment - Note: Review comments are made on code diffs or files, not on the PR overview. - Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### 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. Note: For conversation with the bot, please use the review comments on code diffs or files. ### 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](https://coderabbit.ai/integrations/coderabbit-overrides.v2.json). - 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`
vercel[bot] commented 11 months ago

@levino is attempting to deploy a commit to the thomasdavis's Team Team on Vercel.

A member of the Team first needs to authorize it.

levino commented 11 months ago

Thanks for the invite @thomasdavis ! I still cannot authorize the registry deployment. I can however merge this PR with the check failing. I think we should protect master better and disallow merging of PRs with failing checks.

thomasdavis commented 11 months ago

Thanks for the invite @thomasdavis ! I still cannot authorize the registry deployment. I can however merge this PR with the check failing. I think we should protect master better and disallow merging of PRs with failing checks.

What is your vercel email?

levino commented 11 months ago

What is your vercel email?

Looks like you found it :)

levino commented 11 months ago

If you do not object, I will go ahead and merge. But we could also agree on giving a thumbs up in form of an approving review or something. Might even enforce it as a github branch protection rule. I usually do that.

thomasdavis commented 11 months ago

You can just merge liberally for now. As long as nothing breaks.