Best practice: git, github, lighthouse and 2 developers

Posted by Alxandr on Stack Overflow See other posts from Stack Overflow or by Alxandr
Published on 2010-03-12T13:43:13Z Indexed on 2010/03/12 13:47 UTC
Read the original article Hit count: 435

Filed under:
|
|

I'm setting up a new project and plan on using git and github for sourcecontroll and hosting of repo and lighthouse for bugtracking. I've been working with git for some while now, but only been using it for more of a backup solution than collaborate coding solution.

Also, I've noticed that in github you can setup a servicehook to lighthouse so that whenever you push to github it notifies lighthouse of the changes. This uses a token for user-authentication and has the ability to change tickets to resolved etc.

However, this token I believe functions that way so that whenever a user pushes to the repo (dosn't matter who), it's the owner of the repo that "updates" to lighthouse. This is a problem.

So, I believe it is necessary with 2 separate repos at github (one for each dev), and I'm wondering about the workflow that should be used.

Any1 care to shred any light on this matter? Like when to pull and push (and where), and how to make the two github repos in sync or something like that? Or another solution to the problem altogether.

© Stack Overflow or respective owner

Related posts about git

Related posts about github