IssueRaiser

Settings: Add option for disabling the fork button on repositories.

I would like the option to disable forking original repositories if the developer(s) do not want forks that then people could end up with out of date forks. Or maybe an option so when someone does fork the original repository, if it has branches that was deleted, or unchanged and the main one added commits to (like an unchanged master branch) that the fork would automatically update according to the repository that it is forked on. Also maybe disable fork of a fork of a fork as that becomes confusing as well sometimes. Basically I think a fork that does not have a branch that has a opened pull request, or that does not contribute any changes whatsoever should be automatically managed by github itself as sometimes the forkee does not care to update it themself.

Posted by AraHaan on Jun 14, 2018, 11:55 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.4,000 issues0 comments

github (Software)

Settings: Add option for disabling the fork button on repositories.

AraHaanJun 14, 2018, 11:55 PM

I would like the option to disable forking original repositories if the developer(s) do not want forks that then people could end up with out of date forks. Or maybe an option so when someone does fork the original repository, if it has branches that was deleted, or unchanged and the main one added commits to (like an unchanged master branch) that the fork would automatically update according to the repository that it is forked on. Also maybe disable fork of a fork of a fork as that becomes confusing as well sometimes. Basically I think a fork that does not have a branch that has a opened pull request, or that does not contribute any changes whatsoever should be automatically managed by github itself as sometimes the forkee does not care to update it themself.

Comments (0)

No comments yet. Start the discussion.

Comment on this issue