Closed hnawar closed 3 months ago
And @hnawar I would say you would want to test this with an actual service account and verify it works.
I have tested this with a service account and can confirm it is passed on and the VM was using the service account specified.
In that case, we just need @johanneskoester blessing.
[!WARNING]
Rate limit exceeded
@johanneskoester has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 12 minutes and 40 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](https://coderabbit.ai/docs/faq) for further information.Commits
Files that changed from the base of the PR and between 61b6fe0e92a7cd2b43f2e804c7634c29f5390f4a and 152b9bfc0eb90cf8a1de985924c39111cef2a16f.
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?
In that case, we just need @johanneskoester blessing.
Ok, fine with me.
Merged into non-fork PR #52 for testing with our credentials.
@vsoch @johanneskoester I am supporting a snakemake user to migrate to Batch, one of the requirement that came up was the use of custom service account.
This is my attempt to add support for it, I would appreciate your guidance on how best to contribute and test this PR