Skip to main content

Proposals & Apply

All mutations in BlocPad CLI go through a safe propose → review → apply pipeline. Changes are stored locally until you explicitly apply them to the server.

How it works

  1. Propose: queue one or more changes locally (stored in ~/.config/blocpad-cli/proposals.json).
  2. Review: inspect pending proposals and preview what will happen.
  3. Apply: send the changes to the BlocPad API with an interactive confirmation step.

Task proposals

Goal proposals (Traditional PM)

Epic proposals (Traditional PM)

Story proposals (Traditional PM)

Sprint proposals (Traditional PM)

Review pending proposals

Apply proposals

What happens during apply

  1. Loads proposals from local store.
  2. Converts to API change payload.
  3. Calls the preview endpoint to validate.
  4. Shows preview and asks for confirmation (unless --yes).
  5. Calls the apply endpoint with an idempotent request ID.
  6. Removes applied proposals from local store.

Environment variables

  • BLOCPAD_APPLY_NO_CONFIRM=true: skip confirmation (same as --yes).