Why: there is no delete for a saved workflow or a trigger. GET and DELETE /api/workflows/{name} return 404 and DELETE /api/triggers/{name} has no route, so a workflow or trigger that is no longer wanted can only be removed with database access. Every mutable setting must be editable through the control plane.
Done when: a workflow and a trigger can each be deleted from the API and from their dashboard pages. Deleting a workflow that a trigger or another workflow still references is refused with an error naming the references.
**Why**: there is no delete for a saved workflow or a trigger. GET and DELETE /api/workflows/{name} return 404 and DELETE /api/triggers/{name} has no route, so a workflow or trigger that is no longer wanted can only be removed with database access. Every mutable setting must be editable through the control plane.
**Done when**: a workflow and a trigger can each be deleted from the API and from their dashboard pages. Deleting a workflow that a trigger or another workflow still references is refused with an error naming the references.
sam
added the highbug labels 2026-11-21 15:09:41 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Why: there is no delete for a saved workflow or a trigger. GET and DELETE /api/workflows/{name} return 404 and DELETE /api/triggers/{name} has no route, so a workflow or trigger that is no longer wanted can only be removed with database access. Every mutable setting must be editable through the control plane.
Done when: a workflow and a trigger can each be deleted from the API and from their dashboard pages. Deleting a workflow that a trigger or another workflow still references is refused with an error naming the references.