Skip to content

Repository Creation #142957

Oct 29, 2024 · 2 comments · 1 reply
Discussion options

You must be logged in to vote

If your projects are autonomous and require different versioning, CI/CD, or access control, use distinct repositories. Without everything being connected to a single large repository, it is simpler to handle each project separately.

On the other side, when projects are closely related and share dependencies or code, a single repository with folders functions effectively. By keeping everything in one location, atomic commits provide unified access and facilitate changes across projects.

To put it succinctly, utilize several repos for projects that are only loosely related; if the projects are strongly tied and you wish to manage them more efficiently, keep with one repository.

Replies: 2 comments 1 reply

Comment options

You must be logged in to vote
1 reply
@okoko-sunday
Comment options

Answer selected by okoko-sunday
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Repositories The core of version-controlled code storage New User Help ❓ New User help
2 participants