I just read a very interesting blog post on the Github Blog : “How we use Pull Requests to build GitHub”
I think their solution to track features is very clever, I will try to mimic their solution using GitlabHQ merge requests.
I will be one of the 1200 geeks in Paris to attend the first edition of the famous Devoxx conference in France. I will try to give feedback here on the keynotes I attend throughout the 3 days of this conference. Stay tuned…
Have a look at the teaser :
At work, we made the move from subversion to git as our version control tool. I used git for a few times before we migrate the whole project thanks to the git-svn bridge, and, apart from the usual headache when it comes to merging branches, I was rather convinced we would make the migration to git. To explain what branching model I was expecting to use, I dig the Internet for a good tool, hoping to migrate our so “1.0″ Trac version control and issue management to a more github like one.
There is not as much tools as I first thought, I found gitorious, which seems to be a good tool, but it looks complicated to setup and lacks (or I didn’t find it) a good graphical representation of the branches in the repository.
I came across gitlabhq, which is a starting project, but promising as it aims to mimic github in many ways. I’ve tried it and I must say I am very impressed, it is now one of the tool we use internally, it is not yet a perfect tool but it does its jobs very well. We still use our old Trac environment with git integration to hunt down our bugs and control ticket workflow with commit messages (blog post to come). We also use Trac’s wiki to write our internal documentation toward developpers.
Continue reading