Commit Driven Development

Re:Commit Driven Development by unfoldedorigami on Wednesday August 15, 2012 @01:11PM (#4386969)

I'm not sold on doing this at the commit level, but we have been using Pull Requests on Github in this fashion for Wufoo and SurveyMonkey. We start with an initial commit to start the branch for a new feature and then immediately initiate a Pull Request. That pull request contains a list of items that need to be done for the feature and as it gets developed you can see how commits are working towards making that pull request ready. This also helps tremendously with code reviews because you can do them as the feature is being developed.

What's nice about this method for us is that you can just look at the list of active pull requests for a project and see what features are in active development and get an easy way to drill down into the progress of each.

I guess you could call it Pull Request Driven Development.

[ Parent | on HN ]

Re:Commit Driven Development by ericclemmons on Thursday August 16, 2012 @03:27PM (#4393191)

We do something quite similar.

Because issues and PRs are hopelessly intermingled in Github, we create issues with the sole intent of creating an initial PR "feature/1234-api-auth" so we can reference and close the initial ticket.

The issue describes what is the problem and what needs to be accomplished, while the PR body describes what actions will be taken and the overall progress.

[ Parent | on HN ]