Howdy! Adam Jacob wrote: > On Fri, May 23, 2008 at 11:33 AM, Adam Jacob <[EMAIL PROTECTED]> wrote: >>> That's a good point -- another option is to just extend the -commits >>> list so that everyone posts their commits to it, rather than just the >>> commits sent to the master repo. >>> >>> Anyone want to set up a commit hook for github that would make this >>> easy? > > This is done.
Great minds! I was just in the middle of writing one :D > > Set your commit hook to point to: > > http://git.hjksolutions.com:4011/commit > > And it will relay your commits to puppet-commit via the commitbot. I'll disable the one on git.junglist.gen.nz ;) > > You can see the source at: > > http://github.com/adamhjk/github-commit-email/tree/master Was fun to write anyway - http://github.com/fujin/hooknsling/tree/master - I much prefer the look of your Merb one, though. > It's dead simple, so feel free to tweak it. It'd probably be cool to extend it so we can get the output to call git-diff to show which files changed, like the example .git/post-commit hook. If you could somehow get an array of every file changed in that commit, you could get the content of the diff from scraping the URL.. e.g. http://github.com/fujin/hooknsling/tree/e7cfbd9a8ea3c4dd27523ae459803079b7901ced/app/controllers/push_controller.rb http://github.com/fujin/hooknsling/tree/e7cfbd9a8ea3c4dd27523ae459803079b7901ced%2Fapp%2Fcontrollers%2Fpush_controller.rb?raw=true Would it be too much to attach .patches to the email with multipart mime? - this will get the so called 'code visibility' that we are after. > > Adam > Regards, AJ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en -~----------~----~----~----~------~----~------~--~---
