In a previous article I wrote that I will something about feature-branches. This is the way we will develop the AnonToolBox or telling it better: Following the GitHub Flow!
Atm I have not the time to write a long post to describe the Github Flow and kindly I don’t have to do that, it was already done by Scott Chacon’s article “GitHub Flow”
To use all aspects of GitHub Flow, we always need people with skills present for reviewing the code and a Continuous Integration System for playing with unittests.
But hey, keep the stuff simple at the beginning.
We just have one mission: Anything in the AnonToolBox master branch is deployable!
To get this working, it’s simple forbidden to hack any feature in the master branch. All features => in feature branches.
If you already hack this way, great!
If you do not already hack this way: You will start loving it xD
It’s very simple to branch in a git repo and so it’s very simple to use a branch for each new feature you’re trying to implement.
If you’re in the master branch of a freshly cloned AnonToolBox, a simple
git branch feature--FEATURENAME git checkout feature--FEATURENAME
and you’re in business!
You can even branch from feature-branches, great yea?
Finally, when your new feature is ready and your unittest “smiles green”, you checkout the master branch again and merge the feature-branch. If you’re not sure about the handling, send me a note.
Hopy this post helps you!