CODEWITHSUNDEEP
gitgithubversion-controlbitbucket
Meeesh
Meeesh

Reputation: 1042

With Git, how do I organize code so that every developer gets their own branch (or similar) to test out and develop their own code?

I starting to get into Git and got into it for more convenient development.

I am working on an independent video game with a small team, and I want to have a branch for each developer. When ready we would transfer to the master branch. The problem is that branches are just pointers for commits (I believe?) so with each developer working on different parts of the code (algorithms, GUIs, math, etc.), how will we develop separately?

With branches, the files still go to each other even for test branches with placeholders, and when the others synchronise, their files still get the files from the test branch.

I heard about orphan branches; do those have separate files from each other? I am OK with not using branches, but what do you think is the best way for me to go with this?

Upvotes: 0

Views: 81

Answers (1)

eckes
eckes

Reputation: 67047

You don't do this at all.

In Git, every developer even has her own repository (at least one) where she works out new features. Once she's done, she could publish her features to your blessed upstream repo where her repo was cloned from.

Have a read at the Distributed Workflows chapter of the Git book. This will give you a lot of useful insights to how things work with Git.

Upvotes: 2

Related Questions