The latest articles on DEV Community by Pedro Bufulin (@pedrohba1). https://dev.to/pedrohba1 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F163290%2Fe5b12701-2979-4f7b-bea4-e31837cf0e60.jpg https://dev.to/pedrohba1 en Pedro Bufulin Tue, 01 Oct 2019 01:09:26 +0000 https://dev.to/pedrohba1/did-you-ever-struggle-with-git-31np https://dev.to/pedrohba1/did-you-ever-struggle-with-git-31np <p>I'm in my first job now, and it is a startup. The developers aren't top notch (me neither) but we get things done and learn together how to accomplish complex stuff. <br> But there is one thing that we aren't coordinating quite right, that is the git repo.</p> <p>It is messy, there are many commits in the dev branch that are not going to be in the master branch. We don't make branches specific for features, so almost every time something that shouldn't go goes to master branch. We mostly commit in the dev branch, which is not a good thing to do, and causes the problem that I stated before.</p> <p>So, thing is, I think there is no uniform way to do this that everyone does, but there a few things that I started doing that helped a lot. For example, now I only develop in branches, and all of them are changes in a single specific feature. All branches come from master, so it avoids unexpected problems in production.</p> <p>Still, there are sometimes a struggle, with merges, and conflicts. Because sometimes features touch each other, or people have the same idea over naming stuff. And it frustrates me a lot, because most of the time I need to fix things that are consuming time that I should be developing the feature I want to deploy.</p> <p>How did you have a hard time with git? How do you manage avoiding it?</p> discuss git