Some way to filter "destructive" options #3964

Can we also have a checkbox (checked by default) for pr-branch-auto-delete?

When I recommended Refined GitHub to two groups of my friends, they were both surprised to find that the merged branch was deleted by the extension. Some of them even disabled the extension worrying that it may have more "unexpected" behaviors.

I didn't expect this either. The intention of the feature has no issue from my perspective, but the implementation can certainly be improved, reasons:

• People will likely to notice the feature before it actually does anything.
  • Yes, the deletion is easily reversible, but the deletion itself can cause side effects. Not a very practical example: deleting a branch may cause a Continuous Development service to unassign a preview domain which may be in use.
  • Deletion is a destructive operation inherently, and this issue is (kind of) about making them more noticeable.
• Not everyone is seasoned enough to know the existence of protected branches, and they are paid features for private repos.
• As mentioned in #3636, this feature may make sense most of the time, but it won't suit every workflow, in which case it is reasonable to disable it temporarily.

---

More about my first point (could have already been considered though): many issues are opened because people are unfamiliar with some certain features. We have changelogs and #4004 which inform existing users with new features, but new users will either need to deal with every unfamiliarities or read the lengthy readme. We could have a list of these "destructive" or "controversial" features in the "Welcome to Refined GitHub" issue or somewhere else.