executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
glab-securefileManage secure files for CI/CD including upload, download, list, and delete operations. Use when storing sensitive files for pipelines, managing certificates, or handling secure configuration files. Triggers on secure file, CI secrets, certificates, secure config.
Independent GitHub snapshot · Automated classification · Original documentation governs
Store up to 100 files for secure use in CI/CD pipelines. Secure files are
stored outside of your project's repository, not in version control.
It is safe to store sensitive information in these files. Both plain text
and binary files are supported, but they must be smaller than 5 MB.
USAGE
glab securefile <command> [command] [--flags]
COMMANDS
create <fileName> <inputFilePath> Create a new project secure file.
download <fileID> [--flags] Download a secure file for a project.
get <fileID> Get details of a project secure file. (GitLab 18.0 and later)
list [--flags] List secure files for a project.
remove <fileID> [--flags] Remove a secure file.
FLAGS
-h --help Show help for this command.
-R --repo Select another repository. Can use either `OWNER/REPO` or `GROUP/NAMESPACE/REPO` format. Also accepts full URL or Git URL.
glab securefile --help
See references/commands.md for full --help output.