Can it work when the forked gh repo contains many packages that sometimes use each other? It feels weird to be masking the very repo I cloned to work in...
Now I am using the approach outlined by Francesc Campoy in http://blog.campoy.cat/2014/03/github-and-go-forking-pull-requests-and.html Neat but it feels like cheating... On Fri, Sep 2, 2016, 00:51 Henrik Johansson <dahankz...@gmail.com> wrote: > I did try it but perhaps I did something wrong. > Is 'glide update' enough after such an addition? > > The cloned repo has a glide.yaml and lock file checked in so these would > have to be kept local or otherwise skipped in pull requests I guess. > > On Thu, Sep 1, 2016, 23:43 mhhcbon <cpasmaboiteas...@gmail.com> wrote: > >> this helps ? >> >> https://github.com/Masterminds/glide/blob/a20b232c135529d4d73b5cf95f66954d34750ced/docs/example-glide.yaml#L30 >> >> >> Le jeudi 1 septembre 2016 22:15:27 UTC+2, Henrik Johansson a écrit : >>> >>> Hi, >>> >>> How does the aliasing support in Glide work. >>> There is a couple of hints in the Github readme that it can help when >>> working with forks. >>> I can't find anything in the otherwise nice documentation pages. >>> >>> Anyone knows how to use this feature? >>> >>> / Henrik >>> >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "golang-nuts" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to golang-nuts+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
