git.git style workflow, GitHub and Lighthouse

Thell Fowler's Avatar

Thell Fowler

08 Oct, 2009 06:23 PM

Hi!

A couple of questions in regards to workflow setup for using Github and Lighthouse for contributors.

Our project has a GitHub repository, people then fork from that, branch from master for their topic and then push their topic branch to their own Github account and send a pull request. Once that happens that topic gets merged into out pu branch then graduates to next/master as appropriate.

We've just setup with Lighthouse and I'm not sure how we can use the workflow style of the git project while using Github and Lighthouse. While testing today I found that if a topic-branch is pushed to my personal forked repository with a lighthouse ticket reference in it lighthouse does not learn about it until that topic branch is merged into my own master branch.

Are you aware of a way to setup this workflow? I've found a contributor guide for spreecommerce that is very similar to what we are shooting for, and will be asking them (and the Github staff) as well.

Thanks for reading.
Thell

  1. 1 Posted by Rick on 13 Nov, 2009 06:07 PM

    Rick's Avatar

    This is an issue with Github, and not Lighthouse specifically. Github doesn't always send post-commit hooks. You can setup your own with git post-commit or pre-receive hooks too: http://obvcode.blogspot.com/2007/10/using-git-with-lighthouse.html

  2. Rick closed this discussion on 13 Nov, 2009 06:07 PM.

Discussions are closed to public comments.
If you need help with Lighthouse please start a new discussion.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac