oh weird, I use it globally as convenience for cloning and looking at PRs / never tried using as 'top level' …it does work for that use case currently without any env variables or passing anything. just works from cwd. (and you could make that assumption generally imo)
On Fri, Jun 6, 2014 at 10:18 AM, Andrew Grieve <agri...@chromium.org> wrote: > There's definitely some upside, but some downsides as well: > - would add some overhead for us to have to remember to version & publish > it after every change > - you then need to npm update coho separately from updating all your other > repos (via coho repo-update) > - coho currently puts all repos as siblings to itself, if it's installed > globally, you'd need to pass --chdir path/to/my/git/repos every time you > call it. We could fix this with an ENV_VAR, but it's kinda nice that it > "just works" so long as you have it checked out & npm link'ed > > > On Fri, Jun 6, 2014 at 1:13 PM, Brian LeRoux <b...@brian.io> wrote: > > > I don't see why not. Its pretty damn good now and would only help onboard > > more contributors. > > >
