On 06/25/2010 10:10 AM, Andreas Hocevar wrote: > I like this. It is more efficient than working with patches, and in github we > can even add comments to changesets and code lines. We should, however, be > able to link such branches to (trac) tickets somehow, for a similar workflow > as tickets with patches that can be reviewed by other devs. Any ideas? The > only way I can imagine is to link to github on a ticket, which is not so bad. > Maybe other projects have solved this already? > I don't see any problems with explicitly writing github links on a ticket (seems just as easy as attaching a patch to me). Another, perhaps complementary, practice would be to name branches in git after trac issues. So if you want to get the work I've done on issue #523, you just run:
$ git fetch dwins issue-523 In combination with the github Fork Queue (http://github.com/blog/270-the-fork-queue) this could be a pretty lightweight way to deal with tracking tickets/branches. -- David Winslow OpenGeo - http://opengeo.org/
