Run a workflow
Run Workflow… starts a workflow that can be run by hand, such as a GitHub Actions workflow with a workflow_dispatch trigger or a Bitbucket custom pipeline. GitTree reads its inputs from the workflow file at the branch you choose and shows a field for each.
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.
- A workflow that can be run by hand, and permission to run it.
Where to find it
- The CI/CD view or the palette: Run Workflow…; right-click a branch: Run Workflow on Branch….
| Action | macOS | Windows and Linux |
|---|---|---|
| Show CI/CD | ⌥P | Alt+P |
Steps
Choose the workflow and branch
Open Run Workflow…, pick the Workflow (or Pipeline) and the Branch or tag to run it on.
Fill the inputs
GitTree shows Inputs (from … at …), one field per input, with required ones marked. Inputs are visible to everyone who can see the run.
Run it
Press Run Workflow. If it deploys to a protected environment, GitTree asks Run and deploy to …? first.
Expected result
A new run starts on the branch you chose and appears at the top of the list.
Secured variables
Where the provider has secured variables (Bitbucket), add each by name under Secured variables. When you run, a system dialog asks for each value; GitTree never shows or stores it.
If something goes wrong
“No workflow here can be run by hand.”
On GitHub, add a workflow_dispatch trigger to a workflow file; on Bitbucket, add a pipeline under pipelines: custom:.
“The inputs could not be read from the file, so add them by name.”
Use Add input for each name and value the workflow expects.
Questions
Can I run it on a branch that is not listed?
Yes. Not every branch may be listed; type its name to use it.