On Tue, Jul 10, 2012 at 2:52 PM, Vighnesh Rege <[email protected]>wrote:
> Hey guys, > > Would you have any recommendations for bug-tracking/code-review tools > that works very well with Heroku app git repos? > I was thinking of creating a separate repo on github and pushing to > both - that seems like a lot of work though. > I think that's what almost everyone does. I've seen very few production apps where Heroku is the only git remote and is treated as origin. It's only a tiny bit of extra work to push twice after merging, and Issues and Pull Requests alone are totally worth the effort (aside from the rest of GitHub). If you want to save that keystroke, create a remote alias that includes multiple origin URLs: http://marc.info/?l=git&m=116231242118202&w=2 Finally, that "problem" of having multiple remotes becomes a huge benefit if - in practice, when - a branch has commits that aren't deployable. Hope this helps, Troy -- @troyd // @papertrailapp -- You received this message because you are subscribed to the Google Groups "Heroku" group. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en
