Is there any reason to follow the main -> develop -> feature/my-feature pattern when doing a project alone?

Question

git

For a long time, I used to do projects alone and push everything to master :) (this was after I stopped saving versions to different folders))))

Then, as I participated in team projects, I somehow got used to the scheme: main -> develop -> feature/my-feature and did so purely on the machine, even when I led the project alone.

But now I thought again:

- What for do I need these feature / my-feature - when I work alone?

Because in the end it creates an extra headache with these constant rebases from develop and so on.

The question is:

- Is there at least one rational reason to systematically do more than two branches (main and develop) when you are doing a project completely on your own?

No, it’s clear that sometimes you want to test something there, and periodically you make new branches :)

But so that it’s so constant, systematic, every new feature in your branch.

Or am I missing something here that needs to be taken into account?

Thanks

Answer 1

Or am I missing something here that needs to be taken into account?

Usually, in the master / main branch there is stable code that is tested, and it can be uploaded to the prod.
So if you write 1, it’s quite possible to leave the master-develop division.
But if you need to work on several features at the same time (for example, in one branch - the main feature, in another - you just update the frameworks), then it’s better to divide after all.