After reading Getting Good With Git, I’ve learnt how to use Git, but not how I should implement it while developing. eg. When should I branch/merge, what are tags and what should I do with them?
— Currently I’m a solo dev of this project.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
After reading Getting Good With Git, I’ve learnt how to use Git, but not how I should implement it while developing. eg. When should I branch/merge, what are tags and what should I do with them?
— Currently I’m a solo dev of this project.
If you’re the sole developer and you’re just doing development, simply work on the
masterbranch.If you’re making regular releases, tag your releases with
git tag -a. With a tag, it’s easy to go back and make a branch from that point if you need to fix something in production.If you’re working on experimental new features that might take a while to get right, consider making branches for your work. With separate branches you can easily have multiple ideas in development at once.
For an example of a complex development environment, have a look at A successful Git branching model. If you’re disciplined, that model is doable even for single-developer projects. But it’s not required at all.