Ask Nour about a pipeline failure
Explain Failure opens Nour with a question about a failed run. Nour reads the failing step’s log (at most 64 KiB) only if you approve, every time, and answers with what it thinks went wrong and what to try. Treat the answer as advice: check it against the log.
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: Nour and CI/CD are part of Pro.
- Nour set up with a coding-agent CLI (Set up Nour).
Where to find it
- A failed run: Explain Failure; the palette: Explain Failure with Nour.
| Action | macOS | Windows and Linux |
|---|---|---|
| Open or close Nour | ⌘⇧Space | Ctrl+Shift+Space |
Steps
Open the failed run
Select the failed run and press Explain Failure. Nour opens with a question about it.
Approve reading the log
Nour asks to read the failing step’s log. Approve it to send that log, or decline and nothing is read.
Check the answer
Read Nour’s explanation, compare it with the log, and change your code or workflow yourself.
Expected result
You have a likely cause and a next step, checked against the log.
If something goes wrong
“Only a failed run can be explained.”
Pick a run whose state is failed.
Questions
Where does the log go?
To the coding-agent CLI you set up for Nour, which runs on your computer and talks to its own provider under its own policy. GitTree sends nothing until you approve.