DEV Community

Discussion on: Git Workflow: Do you commit to master on your solo projects?

Collapse
 
darkwiiplayer profile image
𒎏Wii 🏳️‍⚧️

I've never seen much of a point in branches for most cases.

There's lots of cases where you aren't necessarily working on a huge new feature but just need to adjust some details of the behavior, so why bother creating a branch for that?

Even when working with someone else; in most cases I will pull, work on some feature, then (pull again and) push. If some work has been pushed in the meantime, there will be a merge at that point anyway.

Branches are for when your project actually branches off and both branches will be worked on in parallel. Using branches for anything else, in my opinion, is just silly and serves no purpose.

Collapse
 
marcus-sa profile image
Marcus S. Abildskov • Edited

I see you haven't had the need of CI/CD yet, otherwise you would've known the point of Gitflow.

Collapse
 
quii profile image
Chris James • Edited

You don't need gitflow for CI or CD.. at all. How did you come to this conclusion? If anything gitflow is an obstruction to CI.

Collapse
 
woody_tanner profile image
Tanner Woody

I drive to work using the interstate. Other people use the interstate to transport cargo from warehouse to retailer. Those other people aren't silly. People use things for different purposes.

But this is more like saying seat belts are silly because I'm never involved in accidents 😂