News for hackers. Stuff that matters.
Re:How We Make Trello by grmarcil on Thursday March 13, 2014 @01:31PM (#7393291)
Yep. My team follows a similar workflow with Github - every feature, bugfix, etc is developed on a branch off of master, then merged back into master via pull request when it is ready for deploying.

It's a nice workflow, changes are very visible to the entire team and well summarized (by the commit history and any comments/discussion on the pull request itself). Making a new branch is a one-line operation (two if you count hooking it up to the remote), so no, I've never personally felt that was a drag. Sometimes it feels a bit silly to create a branch for a one or two line fix, but the visibility to the team is worth it.

Re:How We Make Trello by sidcool on Thursday March 13, 2014 @01:36PM (#7393316)
Developers in my team have quite a distaste for merging. We try to keep it at minimum. The trade off is less visibility. I agree with you.