Remove old files you no longer need
Normal sending never deletes anything. For a managed set of files there are three separate, deliberate actions.
You need
The pipeit CLI (Linux, macOS, Windows), signed in, and the rights each command needs.
Normal sending and update do not delete additional files. For an explicitly managed set of files there are three separate actions:
- **Apply files /
managed apply:** adopt the delivered contents into the authorized set. - **Remove files no longer included /
managed prune:** bring your own managed set in line with the delivered state. Unrelated foreign files stay protected. - **Remove managed files /
managed delete:** explicitly remove your own managed set, without needing a new transfer as a pretext.
B must first configure a valid receiver policy with exact actor rights and budgets. A send right or a destination is not enough. The receiver defines exactly who may apply, prune or delete, and with which budgets.
The normal manual steps after such a job has been prepared:
pipeit managed preview ACTION-ID
pipeit managed approve ACTION-ID --plan-hash VERIFIED-PLAN-HASH
pipeit managed wait ACTION-IDFirst read the decrypted scope, then confirm exactly that hash. Unattended CI needs an explicitly limited CI policy; --unattended does not grant these rights by itself. Status, resume, cancel, recovery and quarantine care are separate actions. A finished transfer is not a confirmation of a deletion or an activation.
Related guides
- Command line and servers
Store, update or activate a folder
Three receiving modes with different effects, and what none of them does.
- Command line and servers
A CI step with a verifiable result
Deliver a folder from a pipeline and let the exit code decide whether the next step may run.
- Command line and servers
Example: deliver the contents of a website
Send a build as a prepared state and switch to it deliberately afterwards.
Still stuck?
Check the troubleshooting guide first. If that does not help, tell us what happened.