Add an option to allow syncing with upstream even if nobody has rights to push and merge to a protected branch
<!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal #### Issue When creating a fork that I use to create merge requests to upstream, I like to fully lock up the master branch so that I don't accidentally push into that. Sadly this also locks up upstream syncing. To sync upstream you need to go the the settings and unlock the branch temporarily #### Solution Add an option to allow upstream syncing even if the branch is fully locked down. This is an option in github and it helps a lot. It reduces the need to go into the setting to unlock the branch temporarily <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. --> <!-- Label reminders Use the following resources to find the appropriate labels: - Use only one tier label choosing the lowest tier this is intended for - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->
issue