GitTree desktop manual
CI/CD
Your pipelines next to your commits: what ran, what failed and why, without leaving the app.
CI/CD runs
GitTree shows the CI/CD runs of your repository’s host, such as GitHub Actions, in the left panel and in a full list beside the graph: what passed, what failed and why, with Re-run Failed Jobs, Cancel Run… and Run Workflow…. CI/CD is part of GitTree Pro.
ProBrowse and filter runs
The CI/CD list shows every run of the repository and updates by itself while runs are going. Filters narrow it by Branch, Workflow, Status and Trigger; Mine keeps your runs; Watch keeps a run updating in the background and tells you when it finishes.
ProRead jobs and logs
Open a run and select a job or step to read its log in the Log tab. Jump to first error goes straight to the failure, Search the log… finds text, Timestamps and Wrap change the view, Following keeps a running job’s live output in view, and Save Log… writes it to a file.
ProRerun or cancel a pipeline
From a run, Re-run Failed Jobs repeats only what failed, Re-run All Jobs repeats everything, and a job’s menu re-runs just that job (Retry Stage on GitLab-style stages). Cancel Run… stops it; Force Cancel Run… ends it without letting jobs clean up. Neither cancel can be undone.
ProRun a workflow
Run Workflow… starts a workflow that can be run by hand, such as a GitHub Actions workflow with a
Proworkflow_dispatchtrigger or a Bitbucketcustompipeline. GitTree reads its inputs from the workflow file at the branch you choose and shows a field for each.Download available artifacts
The Artifacts tab of a run lists the files it produced, with Name, Size and when it Expires. Save… asks where to save it and downloads it there, as the provider stores it; a zip is saved as a zip and GitTree does not open it.
ProInspect deployments and environments
A run that deploys shows Deploys to … and an Environments tab: each environment, its deployment, branch or commit and when. A deployment that waits shows Waiting for approval; if you are one of its reviewers, Approve Deployment… and Reject Deployment… act on it. These change things for everyone and cannot be undone.
ProCreate and check pipeline files
New CI/CD File… writes a starter file where your provider reads it, such as
Pro.github/workflows/or.gitlab-ci.yml; it never writes over an existing file. Edit it in GitTree, press Check with … to have the provider validate it, then commit it like any file.Manage pipeline settings
CI/CD Settings shows what the provider lets another app manage: Variables, Secrets, Environments, Runners, Schedules, Caches, Definitions and Releases. A secret’s value is typed in a secure system prompt or read from a file you choose, and goes straight to the provider; GitTree never shows, keeps or sends it anywhere else.
ProUse pipeline release controls
CI/CD Settings › Releases lists the repository’s releases. New Release names a tag (or creates one from a branch or commit), with a Title, Notes (Markdown) and files people can download. A release is published for everyone who can see the repository unless you Save as a draft.
ProAsk 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.
Pro