4 ms·
I'd like to have nested projects as well. For instance I want one top-level having my talks, and then sub projects for each talk. Now I either have to clutter m
by maaaats 9y ago
I'd like to have nested projects as well. For instance I want one top-level having my talks, and then sub projects for each talk. Now I either have to clutter my repos with many small projects, or have one big repo with many folders. Which I don't like, as issues, comments, stars etc. should be directed directly to the talk, not a big project.
Other top level projects would be one for various PoCs, learning different languages, programming competitions, maybe one for stuff I did at university etc.
Same for organizations, where I work we now have hundreds of repos in a flat structure. Impossible to manage.
- deleted 9y ago[deleted]
- zwerdlds 9y agoWhat about submodules or subtrees doesn't fit this use case?
- deathanatos 9y agohttps://github.com/isaacs/github/issues/49 https://github.com/isaacs/github/issues/49 — I'd give it an upvote, and if you haven't yet, an email to GitHub support. (I'd like hierarchical repos for both users and orgs.)