3 ms·
Think there are two problems here: 1. For people visiting their own repositories, the viewing the code itself has little to no value. They more than likely alr
by sudhirj 13y ago
Think there are two problems here:
1. For people visiting their own repositories, the viewing the code itself has little to no value. They more than likely already have it open in their editor / IDE in another window. These folks probably want the issues, PRs and other accompanying features. Collaboration is now the key - not the code itself.
2. For other people (non-committers) looking at a repo, this is different. When I visit other codebases I do actually look at the code to check certain things - what style it is, what frameworks have been used, how complicated the code is, if tests are present etc. Then I check to see what kind of (any how many) issues have been raised.
It might actually make sense to show a different view depending on whether you have commit permissions to the repo or not.