Potentially destructive actions should be opt-in and easily identifiable in settings #2318
ChadLevy posted onGitHub
I found that branches were automatically being deleted after pull requests. This causes conflicts with my project's workflow and is nothing something I wish to do.
Github has the option to automatically delete branches after pull requests are closed. I double checked to make sure this option was not enabled. It was not. Then, I looked in Refined Github's settings for this option and found it, automatically enabled, 2/3 of the way down a large list of other options:
I believe potentially destructive actions should be opt-in and easily identifiable in settings. While restoring a branch is trivial, there is still a potential for data loss and as such, whether or not this is done should be left up to the user.