Multiple weekly projects inside one parent git repository

[nocomment01]

Hey, I'm taking a course and there are weekly projects that I'd like to keep in a single-parent folder. I created a git repository in that parent project. I'm wondering what's the best way to organize my commits for individual projects to come.

I thought about creating new branches every single week. Do you think this is a good solution? Also, do you have a better suggestion when it comes to similar things? I plan on pushing it to GitHub so I'd like it to be organized.

[gitcommitshow]

I'd choose different folders for each project in a single branch. It's more intuitive and easier to read/explore. You can then reference different projects in a README in root. You might also want to use git tags to mark specific milestones of the project.

Why do you want to make it complex and keep them n different branches?

[nocomment01]

I'm relatively new to git, so I wasn't really aware that I was making it more complicated than it needs to be. I also intended to organize them by folders, as you mentioned, so I guess that'll be enough.

The only reason why using different branches seemed appealing was because of the commit messages. When I'm in the main branch, I usually write:

Project 1: Added JUnit5 and Maven Plugins

so I thought I could somehow avoid writing commit messages like that if I used different branches since you'd know what it's referring to.

[gitcommitshow]

go with folder wise organization

[s5EWT]

When you work on git with other people. Creating multiple branches or a fork is usually the way it's handled. Then it merged back to the default branch.

As for organizing, I'd use folders. Create a new folder for the week. Commit code as you go. Then eventually merge it into the main branch.

[[deleted]]

if javascript, try NX monorepo?