|
|
|
|
|
by jamessb
2711 days ago
|
|
It seems like the repository type in GitHub already handles several of these cases. A user's list of repositories can already be filtered by "type", and this handles several of his cases: > aicioara-forks — Projects I contributed to. Anything that I pressed “fork” on goes here. These gets automatically classified as type "Forks". > aicioara-old — Repositories that contain code I may want to refer to later, but I do not really want to be associated with. Maybe it’s a high school or university project with no stars and which no longer reflect the way I code. I don’t have time to update them, I still need to refer to them sometime, but I don’t want them to say “hey, this is how Andrei is coding today”. These can be marked as "Archived" (https://help.github.com/articles/archiving-a-github-reposito...) This leaves the "boilerplate" and "gh-pages" categories, which could be indicated by adding prefixes to the corresponding repo names. If the boilerplate code is not intended to be generally useful it could be put in a private repository (especially as all users now have an unlimited number of free private repos |
|