Do any groups find themselves actually creating multiple branches for their project?

Question

Our group works only on the main branch, constantly letting each other know when we are about to push before others push their own code. We think that for the time period we have allocated, creating several versions of the code is hard to keep up with. I was just wondering if anyone has actually used that functionality in git for this specific project out of curiosity. If you do, do you think it makes a big difference in your group's efficiency compared to others?

Answer 1

My team has created multiple branches for our code in this project. I'm not sure if it really increased efficiency (in fact, it may have reduced some efficiency since we are newcomers to it). But it is nice being able to push more often without having to worry about conflicts as much.

Answer 2

My group has created many new branches. At first, I didn't understand why it was important. I forgot to create a new branch once and ended up breaking some code on the main branch, so now I create a new branch each time I start coding a new feature.

Answer 3

Same here. Our group hasn't created multiple branches, but I can definitely see why it might be a wise idea to do so!

Answer 4

I'm in the same group as Lucas and Greyson and I was the one who encouraged all of us to start using branches right around the time of the Sprint 1 demo so now we all work in our own branch and I think it is so helpful!! I never work on the main branch-- even if I am just going to merge my branch with main again right after I make changes I always do it in the branch first. This has allowed all of us to have our own working version of the code. For example, if I am trying to get a certain feature working, I might cause the software to stop compiling while I am working on it, but while I am trying to get this new feature integrated, my teammates do not have to deal with my broken code and can each work on their own code in their own branches without having to deal with the compiler errors that I am having. In short, I would highly recommend using branches-- it reduces a lot of conflicts and makes our work much more efficient!!

Answer 5

my group initially planned to work with branches but after talking to professor Stonedahl he emphasized that it's not gonna increase our efficiency so we stopped. and currently i agree that it wouldn't have just caused additional issues.

Answer 6

We haven't really used branches to add to our code. We have just been making sure to keep up with recent additions and merges. However, I could understand how it could be very useful.

Answer 7

My group hasn't created multiple branches due to not really having a specific need to, but there are fore sure some cases that it would be helpful!

Answer 8

We for sure have. We found that it is really useful to use right before a sprint. Before we kept having to delete our half-finished code because of the potential break it would cause when running. Now we can test out our ideas in a safer setting without that worry.

Answer 9

My group creates branches based on aspects we are working on, some people might even have multiple branches that they are working on if they are working on two separate features.

Answer 10

My group doesn't often create branches because we find ourselves working on it at different times. However, with that said, My group creates branches when we are refactoring things so that if we mess up we can abandon it.

Answer 11

We do but not much. Since we found that it's easier to debug if we do a little commit every time rather than create a new branch and merge those later

Answer 12

Every time we push or commit, our team members inform one another. We also solely work on the main branch. Although having many branches is a great concept, Dr. Stonedahl did point out that we should occasionally combine those branches to maintain a more coherent and stable codebase.

Answer 13

Yes we did, the main branch crashed miserably and we created a testing Branch to avenge out of it we did go back to the main branch again though we did not merge or rebase its still parallel.

Answer 14

did anyone end up rabasing these branches?