What's the best way to automatically always pull the latest release/commit 
for certain repos? We use gerrit internally so all of our import paths for 
internal packages start with something like gerrit.corp. We have over 50 
different repos and it would be painstaking to have to update (pull latest, 
run go get, commit, get review) every single one of those repos whenever an 
internal package was updated with a minor change.

How do others solve the problem of outdated modules? Do developers 
frequently commit "Go modules updated" changes where they just update the 
go.mod? Is there a process defined where every repo has their deps updated 
once a month/week/etc?

1) Would it be better to just remove gerrit.corp lines from go.mod before 
it's committed so the dependencies are always resolved at run-time by CI?
2) Should our CI system look at go.mod and run go get -u for each 
gerrit.corp line as part of the build/test pipeline?
3) Or should we just run "go get -u ..." on every CI build to always have 
the latest minor updates of all modules?

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/909a63a6-0e02-4129-bf5d-efadb353acf4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to