How to organize multiple projects within an Organization on GitHub?

[rintar0315]

Select Topic Area

Question

Body

Hello,

I would like to ask about the best way to organize projects within a GitHub Organization.

Is it possible to create folders inside an Organization to manage multiple projects separately?
Or is it recommended to create individual repositories for each project instead?

I’d appreciate it if you could share the best practices for managing multiple projects in an Organization.

Thank you!

[publicbyte]

You can’t create folders inside a GitHub Organization. The recommended approach is to create a separate repository for each project.
For example, if you’re working on a distributed application with multiple services like AuthService. UserService, PaymentService etc, each of these services should have its own repository within the same organization, since they’re related, that way its easier to maintain and track issues.
If you have other unrelated projects. For example, a project that belong to a different business area or client, you can create another GitHub Organization under the same GitHub account to keep them separate.

[rintar0315]

So, does that mean all repositories under an organization have to be managed at the same level?

Currently, we are using SVN, where we manage our projects by separating them into folders.
In some cases, a single project folder contains multiple source sets.

When migrating to GitHub, does that mean we need to split each source into individual repositories?

[publicbyte]

I mean you could technically keep all your projects in a single repository on Github as well but i wouldnt recommend it, cause its just makes it difficult to manage

[rintar0315]

Thank you for your previous guidance.

I would like to clarify the difference between a common repository and a submodule in practice. Could you please explain:
The concrete differences between using a separate common repository and using a submodule for shared code.
The recommended way to use each approach, including any best practices for managing updates and dependencies.
Any examples or guidance would be greatly appreciated.

Thank you for your support.