The problem with replace is when you want to integrate this within a CI. Hello,
IMO it would be be good, if I could specify a’s version with a branch name like “master” in b’s go.mod and had a way to call something like go mod pkg in a, which would compile a and put it in the pkg folder, maybe together with the git commit hash as meta information. Then in b could check if the upstream branch ref is newer and only then consider the local pkg output as stale. Then once a is in a good shape, push it’s branch. By means of this CI builds of b could pick this up as well. Regards Mirko -- 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.
