Workflow best practice with git and github?

Question

I have been using git and github with my small team of developers for our projects. I can\'t help but think that we aren\'t doing it right. I am interested to hear how other

Answer 1

Basically, you can very well function with one "central" GitHub repository.

• Tags being immutable pointers, they can be used (and pushed) any time, in order to be checked-out to any testing or production environment. That allows some validation to take place but usually does not serve for development.
• Pulling a branch means you can make some evolutions within that branch (due to some bugfix and adjustments to make once the code is on a production environment) and push it back for all the other developer's repository for them to pull back and take into account.

So it depends what you are doing on those servers: only validation (with a status accepted or rejected), or also further developments.
In every case, a tag with an appropriate naming convention is nice to keep track of specific commits in the history, but branches are necessary every time you need to isolate a development effort.