Ask HN: How to handle 500+ repositories in GitHub?
Searching for ways to handle a large number of repositories I stumbled in this thread: https://github.community/t/structuring-repositories-or-organisations/817
Apparently Gitlab and Bitbucket give you a feature to group repositories into projects while Github is lacking something similar.
How companies using Github handle their repositories when there are 100's of them?
Apparently Gitlab and Bitbucket give you a feature to group repositories into projects while Github is lacking something similar.
How companies using Github handle their repositories when there are 100's of them?