Inspect checks and commit status
GitTree shows the CI state of commits and pull requests: Checks passing, Checks failing, Checks running, Checks skipped or No checks reported, with how many passed, failed, ran or were skipped. Select it to see the runs, open a check’s log, or Re-run Check.
Needs GitTree Pro or a running trial; Free keeps every local Git feature. Compare the plans.
On this page
Before you start
- GitTree Pro or a running trial: CI/CD runs are part of Pro.
- An account connected for the repository’s provider, and CI that reports to it.
Where to find it
- The check state beside commits in the graph and on pull requests; the Checks tab of a pull request.
| Action | macOS | Windows and Linux |
|---|---|---|
| Open CI/CD | ⌥P | Alt+P |
Steps
Read the state
Point at a commit’s check state to read, for example, “Checks failing: 4 passed, 1 failed, 0 running, 0 skipped”.
Open the runs
Select it to show the runs for that commit, or open the pull request’s Checks tab.
Read or re-run
Choose Open Check Log in Browser to read a check’s log, or Re-run Check to run it again where the provider allows.
Expected result
You know which check failed and why, and can run it again.
If something goes wrong
“Not every check could be read, so this is not shown as passing.”
Some checks could not be read; open the runs to see them, or refresh later.
“Checks are paused to stay within the provider’s request limits”
GitTree asks again after the time shown. Nothing is lost.
Questions
Why does a commit say “This may be out of date”?
The provider could not be reached; you are seeing the last known checks.