CI/CD
CI/CD
Backups from pipelines: trigger them, wait on them, or upload from a job.
View as MarkdownA pipeline meets saved.sh in one of three ways: trigger an existing backup and move on, trigger and wait so a deploy gates on a fresh copy, or submit an artifact the job itself produced as a manual backup. All three run on an API key with exactly the permissions the job needs, never on a person's session.