On Mon, Sep 13, 2010 at 10:24 PM, Jeff King <peff@xxxxxxxx> wrote: > On Mon, Sep 13, 2010 at 10:47:30PM -0600, Joshua Jensen wrote: >> >Bear in mind that you can still shift to a maintainer model, but keep >> >the maintainer automated. That is, you can queue up "to-pull" heads, and >> >then have an automated process pull them one by one and do some basic QA >> >(does it merge, does it build, does it pass automated tests, etc). Which >> >is not that different from what many shops do in the non-maintainer >> >model, except that when you break the build, the maintainer process >> >notices _before_ publishing the merged tip, so everybody won't try to >> >build on your broken crap. >> >> Do you know of any existing software that does this? This may be >> ideal in the short term. > > I think that Avery Pennarun's gitbuilder may do what you want: > > http://github.com/apenwarr/gitbuilder/ > > but I've never used it. gitbuilder doesn't do this. However, it does let you automatically do user-defined things for each branch, and it stores the result for each one. So it would be a pretty short trip from there to auto-merging when a branch is ready. Have fun, Avery -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html