Source: https://seerepo.com/docs/github-ci
Markdown source: https://seerepo.com/docs/github-ci.md
Description: What SeeRepo reads from your automatic tests, and which commit it points at when they break.

# GitHub and your automatic tests

SeeRepo doesn't run your tests. It hears what your GitHub Actions report about the last commit on your map's branch, through its GitHub App, and you see it in the dock and on the map.

## What SeeRepo reads from your automatic tests (CI)

Each commit keeps its worst result: one check that fails is enough for that commit to count as failing. In your repo's settings, **Automatic tests (CI)** says one of three things:

- **Passing**: the last commit's tests passed.
- **Failing since** a date: the day they broke.
- "This repo runs no automatic tests on GitHub.": nothing has reported yet.

## Which commit it points at

When your tests go from passing to failing, the commit that did it is marked **May come from here**. It's a clue, not a verdict: that commit is the first one that failed.

If they were already failing, no new commit gets marked, so nobody is blamed for what was already broken. When they pass again, the mark goes away.