sincecutoff.com
llms.txt /v1/json
← all changes

circleci project trigger update and delete

Introduced 2026-10-28 · score 0.98

HOW TO USE IT

When changing an existing trigger, run `circleci project trigger update` with at least one setting flag; to remove it, run `circleci project trigger delete` by trigger ID.

circleci project trigger update <trigger-id> --event-preset <preset> --config-ref <ref> --checkout-ref <ref> --json
circleci project trigger delete <trigger-id> --force

WHY THIS HELPS

Manage an existing project trigger from the CLI by updating its settings or deleting it by trigger ID.

BEFORE THIS CHANGE

Use `circleci project trigger list` and `circleci project trigger create`; trigger update and delete were not available.

REQUIREMENTS AND LIMITATIONS

  • Version: v1.12.0
  • Non-interactive: Delete prompts for confirmation; `--force` skips the prompt for scripts.
  • Non-interactive: Update supports `--json` for JSON output.
  • --event-preset <preset>: Choose the trigger event filter preset.
  • --config-ref <ref>: Git ref for fetching config; applies when config repo differs from event source repo.
  • --checkout-ref <ref>: Git ref for checkout; applies when checkout repo differs from event source repo.
  • --enable / --disable: Resume or pause the trigger; mutually exclusive.
  • --json: Output the update response as JSON.
  • --force: Skip delete confirmation prompt.
  • `--enable` and `--disable` are mutually exclusive.
  • Only flags passed to update are sent; passing no update flags is a bad-arguments error.
  • The event source cannot be updated because it is fixed at creation.
  • Neither command requires a project; both address the trigger by ID.
  • Delete confirms in a terminal and requires `--force` otherwise.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card