### Summary It appears like an inconsistency for me. Apart from the logical association, a fork is also created if I would checkout a repository and push it to an organisation (or user) that I'm in control of. Which is why I (and others) were pretty surprised that there seem to be a permission overlap or mismatch on [this repository](https://gitlab.com/etienn01/flauncher). Everybody can check it out but no one can create a fork. See also [this issue](https://gitlab.com/etienn01/flauncher/-/issues/61#note_818661671). ### Steps to reproduce 1. Try to fork [this repository](https://gitlab.com/etienn01/flauncher) ### Example Project [example project](https://gitlab.com/etienn01/flauncher) ### What is the current *bug* behaviour? On the public repository the non-actionable message `You don't have permission to fork this project` is shown. Which is [definitely better than hiding the button](https://gitlab.com/gitlab-org/gitlab/-/commit/01329d6ad7b1033eec01379a3808a5af0ad26871) but still not perfect. ### What is the expected *correct* behaviour? 1. It should be possible to fork a repo if it's possible to check it out (i.e. public repository) 2. It would be helpful to at least extend the message (i.e. adding `Ask an repository admin to activate Forks in "Visibility, project features, permissions" of the repository settings`). 3. If the repository is public and forks are disabled it could show a highlighted warning in permission settings. Maybe something like `Are you sure that you want to disable Forks? Users can check out the source anyway, since the repository is public.` ### Relevant logs and/or screenshots This is the current non-actionable message: <div align="center">  </div> This is how the settings warning _could_ look like: <div align="center">  </div>