<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=415562) </details> <!--IssueSummary end--> <!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "type::bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=type::bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary Recently, gitlab shows a ``` Forked from mirror / ... 1085 commits behind the upstream repository. ``` like information for forked repositories and sometimes there is an "update-fork" button. This is confusing and can be dangerous: - we nearly almost use versioned branches as base for the fork (e.g. linux kernel version v6.1) while base repository has `master` as default branch. The information, how many commits we are behind or ahead the upstream repository is not meaningful in this case and confuses only - we definitively do not want the "update-fork" functionality in the situation above. But "update-fork" works even on protected branches and does not ask for confirmation either. This is dangerous because it changes the code silently. Please add an option to disable this box. ### Screenshots  ---> "Update fork" button exists plus completely meaningless information about ahead/behind  ---> but same branch is protected and user is not allowed to push into it