gocov

README

gocov

Diff coverage, pull request comments and merge gates for GitHub, GitLab and Bitbucket Cloud — an open-source Coveralls/Codecov alternative. Use the hosted service at gocov.dev (public repos free forever, badge included), or self-host the same product: one Go binary plus Postgres.

Coverage on your pull requests in three steps

1. Sign in at app.gocov.dev and pick the workspace gocov should track.
2. Connect it to your forge — one click; on GitHub it is the same App install.
3. Add one step after your tests, no secret needed (GitHub Actions shown):

permissions:
  id-token: write                 # the job proves its identity; nothing to paste
steps:
  - run: npx jest --coverage      # or go test -coverprofile, mvn verify, pytest --cov, ...
  - uses: gocov/gocov-action@v1
    with:
      files: coverage/lcov.info

The job's short-lived identity token replaces the upload secret; a GOCOV_TOKEN secret still works where a CI cannot mint one. The action downloads the CLI binary and checks its sha256, so there is no toolchain to install — the same lines work whatever your tests are written in; point files at whatever your test runner produced. Recipes for the rest: GitLab CI · Bitbucket Pipelines · any other CI · languages & formats

From then on every push carries its own coverage: a status and delta on the commit, a diff-coverage comment on the pull request, a gate that can block the merge, and a badge that is one line of markdown:

[![coverage](https://app.gocov.dev/badge/github/myworkspace/myrepo.svg)](https://app.gocov.dev/repos/github/myworkspace/myrepo?ref=badge)

What you get

• Pull request surfaces: build statuses, PR/MR comments with diff coverage, GitHub check runs and Bitbucket Code Insights report cards with inline annotations on uncovered changed lines — see the tour
• Coverage gate: per-repo minimums for total and diff coverage plus a drop tolerance; a failed gate pushes a FAILED status your forge's merge checks can block on
• Any language: Go cover profiles, LCOV (Jest, Vitest, nyc, c8), JaCoCo XML (Maven, Gradle, Android), Cobertura XML (coverage.py/pytest-cov, coverlet, gcovr), Clover XML (PHPUnit, Istanbul) and SimpleCov resultsets (Ruby) — detected from the uploaded content, no flag needed
• Web UI: repo list, per-file coverage, line-by-line source view with hit counts, coverage trend chart, SVG badge per repo, sign-in with your forge account — a React single-page app compiled at build time and embedded in the server binary, so running gocov is still one binary and Postgres

Self-hosting

The same product on your infrastructure, AGPL-3.0, no telemetry and no call home:

docker compose up

This starts Postgres and the server on http://localhost:8080 (migrations apply automatically). Then enable sign-in with your forge, sign in — the first screen registers your workspace and mints its upload token — and set GOCOV_TOKEN and GOCOV_SERVER in CI.

For a real instance, every release publishes ghcr.io/gocov/gocov-server for amd64 and arm64, and deploy/ has the production compose file: the pinned image behind Caddy (TLS included), Postgres external or bundled, one .env to fill in. The operator's guide — the secret key, your own GitHub App, backups, upgrades — is Self-hosting.

Documentation

The full documentation is at docs.gocov.dev, built from docs/ in this repository:

• Getting started — sign in, one CI step, first report
• Migrating from Codecov or Coveralls — the action inputs, codecov.yml and the Coveralls settings mapped onto gocov, and the order that keeps the old tool running until the numbers agree
• Uploading from CI — GitHub Actions, GitLab CI, Bitbucket Pipelines, other CI systems, languages & formats
• Pull requests · Connect your forge · Coverage gate · Parts · Why coverage changed
• CLI · API & badge
• Self-hosting — production setup, sign-in, forge apps & credentials, configuration, development

License

AGPL-3.0 — see LICENSE.