By default, a command like go build
ignores the vendor directory and will reach out to the network as needed to satisfy imports.
Some teams will not want the go tooling to touch the network in CI, whereas other teams might want greater control during day-to-day work regarding when the go tooling updates go.mod
, how dependencies are obtained, and how vendoring is used.
This list is an attempt to build a more consolidated enumeration of some of the primary knobs and options that people might use to adapt the default Go behavior to better suite their particular use cases. Most of this information is currently spread throughout different sections of the official documentation or modules wiki.
The intent of this list is to help socialize the existence of these knobs, without giving all the detai