Auto-delete feature branches only after final deployment. Current deletion can hinder troubleshooting if pipeline promotion fails.
The current "Auto delete feature branches when there are no PRs open against the branch" setting works well for general cleanup. However, in pipeline-driven deployments, a branch can be deleted even if the change fails to progress to the next stage.
Consider adding an option to delete feature branches only after the deployment successfully reaches the final environment (e.g., Production). This would preserve troubleshooting visibility when pipeline promotion fails and help teams investigate root causes before the branch is removed.
5
votes
Steven
shared this idea