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.
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.
- Admin or maintainer rights on the repository for the settings you change.
Where to find it
- The CI/CD view or the palette: CI/CD Settings.
| Action | macOS | Windows and Linux |
|---|---|---|
| Show CI/CD | ⌥P | Alt+P |
Steps
Open the settings
Choose CI/CD Settings and pick a section such as Secrets. Back to Runs returns to the list.
Add a secret
Press Add Secret, give its name, and choose Where the value comes from: Type it in a secure system prompt or Read it from a file I choose. Tick Protected branches and tags only where offered. Press Continue….
Confirm and enter the value
GitTree asks Store a new secret … in …?. Press Open Secure Prompt (or Choose File) and enter the value outside GitTree’s window. Closing the prompt sends nothing.
Expected result
The secret is stored on the provider, and runs can read it.
What cannot be undone
- Replace … overwrites the current value on the provider; it cannot be recovered.
- Delete … removes it: runs that read it no longer get it, and nothing keeps a copy.
- If the setting changed on the provider since you opened it, nothing is sent; review it and try again.
If something goes wrong
“… are managed in …”
The provider offers no way for another app to list them. Use Open in … to change them on its settings page.
Questions
Can I see a secret’s value in GitTree?
No. Providers never return a secret’s value, and GitTree never shows or stores one.