3

Possible Duplicates:
Are there advantages to using a DVCS for a solo developer?
As a sole developer (for now), how should I be using Git?

I'm a solo developer, and I've been quite comfortable with SVN for a number of years.

My workflow has been the following

  1. create a project on dev workstation and make changes
  2. commit to subversion
  3. pull project to dev notebook and make changes
  4. commit changes
  5. wash, rinse, repeat (no branches)

Now I've recently pushed my first open project to GitHub, and I really like how it all works.

I'm wondering however, what is the best approach to using a DVCS as a solo eveloper. Should one follow the same workflow as SVN and work exclusively on the master, or is it a good idea as a solo developer to fork the project for my two (or possibly more) dev machines?

Any advice on how to approach a GitHub workflow as a solo developer would be greatly appreciated.


EDIT

One thing I've come up with as I continue to wrap my head around this problem is the fact that the "master" repo should only be for fully functioning code.

Therefore I should create a single "working" branch and push it back and forth between my two dev computers. When I feel that I've got the next iteration of fully functioning code, I proceed to push it to the master, but never work directly with the master code.

Thoughts?

marked as duplicate by Matthieu, Josh K Feb 7 '12 at 19:00

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.