glab securefile can update existing files
Introduced 2026-07-21 · score 0.98
HOW TO USE IT
When a project already has the secure file, run `glab securefile update <name> <path> [flags]` to replace its contents. If the contents are unchanged, no update occurs; the update changes the file ID, so later downloads should use `--name`.
glab securefile update "<name>" "<local-path>"glab securefile update "<name>" "<local-path>" -yglab securefile update "<name>" "<local-path>" --repo <owner>/<repo>WHY THIS HELPS
Update an existing secure file through glab.
REQUIREMENTS AND LIMITATIONS
- Version: v1.109.0
- <name> (required): Existing secure file's name.
- <path> (required): Local path to the replacement file.
- -y, --yes: Skip the confirmation prompt.
- -R, --repo <string>: Select another repository; accepts OWNER/REPO, GROUP/NAMESPACE/REPO, a full URL, or a Git URL.
FIRST-PARTY EVIDENCE
- https://gitlab.com/gitlab-org/cli/-/releases/v1.109.0
- https://docs.gitlab.com/ja-jp/cli/securefile/update/
Check the installed version and the source before using it. Entry JSON