Comment 5 for bug 34540

I think we should add the ability for a user to delete a branch as long as it hasn't been pushed to, or subscribed by anyone other than the user themselves.

This is really a non-branch, as there will be nothing on the code hosting filesystem that needs to be cleaned up, and the removal of the branch from the database will be sufficient to clean it up.

Deleting existing code however is more problematic.

I'd suggest a lifecycle_status of "Delete pending". It would automatically be handled by all the current filtering mechanisms.

Any attempt to push to a delete pending branch will fail. Mirroring is not attempted for a delete pending branch.

The removal process could then start at the code hosting filesystem, then the intermediate locations (sftp area), and finally out of the database itself.

We wouldn't then need difficult garbage-collected statuses.