Quickstart
The shortest path from account login to the first Ernest pull request inspection.
Ernest starts reviewing pull requests after the selected GitHub account is connected and at least one repository is active. New GitHub App installations receive Free bonus inspections, so you can verify the first reviews before choosing Dev, Pro, or Enterprise.
Setup checklist
Sign in with GitHub
Open ernest.kubeply.com/app and sign in with the GitHub account that can manage the target organization or account.
Install Ernest
Install Ernest on the GitHub organization or account that owns the repositories.
Enable a repository
Enable at least one synced repository in Ernest.
Review the Free bonus inspections
Use the free inspections Ernest grants after GitHub setup to open or update a pull request in an enabled repository.
Choose a plan
Choose Dev, Pro, or Enterprise when you are ready to keep hosted inspections running beyond the Free bonus balance.
The in-app checklist follows these same steps and shows the free inspection balance when it is available.
Ready state
The dashboard is ready to test when GitHub is connected, at least one repository is active, and the account has remaining Free bonus quota, Dev/Pro monthly quota, or Enterprise unlimited quota.
First inspection
Open or update a pull request in an enabled repository. Ernest should create a GitHub check and then submit a pull request review.
The first inspection can take longer than later inspections because Ernest needs to prepare repository context.
What success looks like
- The GitHub check is created by the Ernest GitHub App.
- If Ernest finds nothing actionable, the pull request is approved without extra review text.
- If Ernest finds issues, it posts concise inline review comments when GitHub accepts the line range.
- If an inline comment cannot be attached, the finding is still summarized in the review output.
Dashboard
The product dashboard is available at:
Use the dashboard to switch organizations, sync repositories, enable or disable repository reviews, manage billing, and inspect setup state.
Local CLI
Use the CLI when you want Ernest to inspect local changes before pushing:
Then authenticate and inspect the current worktree:
See the Local CLI guide for authentication and output format, and the Troubleshooting guide for common issues.
