Public repository can be cloned but not forked
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. Everybody can check it out but no one can create a fork. See also this issue.
Steps to reproduce
- Try to fork this repository
Example Project
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 but still not perfect.
What is the expected correct behaviour?
- It should be possible to fork a repo if it's possible to check it out (i.e. public repository)
- 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). - 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:
This is how the settings warning could look like:
Edited by Alexander Adam