Create and check pipeline files
New CI/CD File… writes a starter file where your provider reads it, such as .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.
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 is part of Pro.
- The repository is open; checking the file needs an account for its host.
Where to find it
- The palette: New CI/CD File… and Check CI/CD File with Provider.
| Action | macOS | Windows and Linux |
|---|---|---|
| The command palette | ⌘⇧P | Ctrl+Shift+P |
Steps
Pick a starter file
Choose New CI/CD File…, then a template under Starter files, such as GitHub Actions: build and test or GitLab CI/CD: build and test stages. Press Create File.
Edit it
The new file opens in the file workspace. Change the commands to your project’s and Save.
Check it with the provider
Press Check with …. GitTree shows … accepts this file. or the Errors and Warnings it reported, and, where the provider offers it, The file as … expands it.
Commit it
Stage and commit the file, and push. The provider runs it on the next push.
Expected result
A CI/CD file the provider accepts is in your repository.
Starter files
- GitHub Actions: build and test, Node.js, Rust, and run by hand with inputs.
- GitLab CI/CD: build and test stages.
- Bitbucket Pipelines: build, test and a custom deploy.
- Azure Pipelines: build and test.
If something goes wrong
“A file is already at …; GitTree never writes over it.”
Edit the existing file instead, or move it first.
“Open the file in the file workspace first.”
Open the CI/CD file, then press Check with ….
Questions
Does checking the file run it?
No. The provider only validates it; nothing runs until you push.