Setup

GitAuto needs a GitHub Actions workflow that runs your test suite and uploads a coverage report as an artifact. This is how GitAuto knows which lines and branches your tests cover.

Automatic setup:When you install GitAuto on a single repository (or add a single repo to an existing installation), it detects your language/framework and opens a pull request with the right workflow file. Check your repo for an open PR titled "Set up test coverage workflow".

You can also trigger this from the Coverage Dashboard or the Coverage Charts page when no coverage data is available.

Manual setup: If you prefer to configure the workflow yourself, follow the guide for your language:

The real goals are fewer bugs, less review burden, confidence when merging, and faster releases. Those are hard to measure directly, so we track test coverage as a practical proxy - not perfect, but simple and actionable.

Once your CI workflow uploads coverage, check the Coverage Charts to see where you stand. Then set a target - 80% is the common standard, 90%+ for regulated codebases (fintech, healthcare), 95%+ for safety-critical systems (aerospace, automotive, medical devices).

Enable the schedule trigger on the Triggers settings page. GitAuto will start creating test PRs on a recurring schedule, and you just review and merge.

To decide how many times per day to set, open the Coverage Dashboard and count how many files still need coverage. Work backwards from your goal: say you have 500 files below 90% and want to reach your target in 3 months - that's roughly 60 business days, so you'd set it to 8-10 times per day.

• Schedule (set-and-forget) - GitAuto creates test PRs on a recurring schedule.
  • Test failure (set-and-forget) - Automatically fixes failing tests in the PR
  • Review comment (on-demand) - Leave comments on the PR to request changes
• Dashboard (on-demand) - Select files on the Coverage Dashboard and click "Create PRs".

For all available triggers, see the Triggers Overview.

Check the PRs GitAuto creates. Make sure tests ran and are passing, review the changes, and merge if they look good. Repeat this cycle until you reach your target coverage.

When you leave review comments, GitAuto learns from your feedback. It persists reusable patterns in a GITAUTO.md file in your repo, so it won't repeat the same mistakes. Over time, you'll need to leave fewer review comments as GitAuto accumulates your team's conventions.

Once you're happy with the results, buy more credits to ramp up - more PRs per day, more repos.