Closed levino closed 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 |
[!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.
@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.
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.
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?
What is your vercel email?
Looks like you found it :)
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.
You can just merge liberally for now. As long as nothing breaks.
also updates the README with the new usage