• Service Integration

    pjhyett Apr 10

    We heard you loud and clear that you wanted to integrate GitHub with your existing services without having to setup a custom post-receive service. Now, when you go to your repository’s edit screen, you’ll see the following:

    Service Hooks

    We knocked out the first two services that we’re most familiar with, Lighthouse and Campfire, but expect to see more coming very soon. Feel free to request a service (or +1 the ticket if your service is already listed) so we know which are the most help to you guys.

    • Comments

    • joshknowles 26 minutes later

      I assume the Lighthouse hook is used to close a ticket. Is there a specific format that that commit message needs to follow?

    • robbyrussell 29 minutes later

      Okay, I set this up and don’t have a clue as to what this does… ;-)

    • feldpost 37 minutes later

      yes, yes, yes! i was just mumbling to myself how much i dislike the post-commit solution! you guys rock!

    • jlindley 39 minutes later

      Lighthouse API
      Basically, use is like this in commit messages-
      Prototype new feature [#15]
      New feature is implemented and tested [#15 tagged:committed responsible:rick milestone:”Launch” state:resolved]

    • pjhyett about 2 hours later

      @robby when you push to github, we pipe all of the commit info info to any of the services you setup. If you use the special syntax that jlindley linked to, Lighthouse will do cool things with it.

    • b3b0p about 2 hours later

      So, this will send a message to campfire when you commit?

    • pjhyett about 3 hours later

      @b3b0p yes, but if you’re on an ssl account, you’ll need to wait a bit longer until we push out support for it.

    • Bill 1 day later

      Woo hoo. I see the messages on my campfire. But my Lighthouse ain’t getting it yet. For “project id” I’m using Lighthouse’s “token name” per these instructions: http://www.lighthouseapp.com/help/using-beacons-and-api-tokens
      Is that right? Or should I be using part of the email identifier used to email tickets into Lighthouse e.g. ticket+name.99-abc32xyz@lighthouseapp.com

    • maddox 1 day later

      for the record, your account(subdomain) is the first part of your lighthouse URL:
      http://jtoe.lighthouseapp.com

    • imagetic 13 days later

      Every commit says it’s me, even when it’s collaborators on my github project…fine for now, but def something I want to see fixed/updated for sure

    • darcy 13 days later

      Very cool feature. I know its new, but wanted to add a +1 for more customization of the integration level – meaning some control of how ‘chatty’ it is. For example, posting all the changesets to lighthouse for me is total overkill and actually a deterent – thats what github is for, lighthouse is for tickets, not repo tracking. Clients (for example) don’t need to see commits, and its better that they don’t.
      Anyhow, great feature, glad to see github going that direction!

    • jash 29 days later

      I couldn’t figure this out very well at first until I found this page:
      http://lighthouseapp.com/help/setting-up-subversion-integration

    Participate

    Please log in to comment.
rss