Turn it on
- Open Settings → Git.
- Switch on Review every repository.
- Check the count: Kody lists how many repositories it will start reviewing, and how many it skips.
- Confirm.
Reviews on these repositories use your credits (or your own model key with BYOK), and pull
request authors in them may take license seats, as on any reviewed repository.
What gets reviewed
- Every repository the credential can see. On GitHub with the Kodus app, that is the repositories the app is installed on. With a token, it is every repository the token’s account can access.
- Not archived repositories. They are always skipped.
- Not forks and mirrors, unless you tick Also review forks and mirrors when turning it on.
New repositories
Kody checks for new repositories every 10 minutes and sets them up the same way as a repository you add by hand: webhook, settings, code graph and recent pull request history.- A pull request opened on a new repository after it was set up gets a review as usual.
- A pull request opened before that (in the first minutes after the repository was created)
is reviewed on its next push, or right away with
@kody start-review. - On GitHub with the Kodus app, a new repository is set up as soon as GitHub reports it. For repositories created after the app was installed with access to all repositories, the app needs the Repository webhook event (self-hosted: add it in your GitHub App settings).
API_CRON_SYNC_ALL_REPOSITORIES (default every 10 minutes).
Leave a repository out
Open the repository’s code review settings and turn off automated review. Kody keeps it that way after every sync, and its pull request authors do not take license seats from automatic reviews.@kody commands still work on it.
While Review every repository is on, repositories cannot be removed from Settings → Git:
the next sync would add them back.
When a repository cannot be set up
Kody needs permission to create a webhook on each repository. When the provider refuses, the repository is listed under Settings → Git with the reason, and Kody retries it on every sync.
If the provider rate-limits Kody while it sets up many repositories, Kody stops and continues on
the next sync, so a large first run can take a few cycles.