Feature Request: Remember most recent choice for branch update strategy

[armovoy]

Select Topic Area

General

Body

Would it be a bad idea to make the choice for updating a branch persistent (most recent shown as default)?

...just as it is remembered for the other split button - merging strategy.

These two split buttons are IMO related - meaning: when your team avoids merge commits in general, you'd probably want to have rebase-driven choices as your convenient split button defaults in every PR.

I don't think it would hurt anyone, regardless of their preference here.
Am I overlooking considerations here?