Description: The Blog of Dan Esparza
blog (30127) portfolio (18325) papermod (242)
When developing with Go on a team, it is useful to have a good branching strategy so you can work together as a team and not tromp on each others changes.
But how do you use Go modules with a branching strategy? It’s easy to refer to another project (even at a certain version ) – but branches seem to offer a bit of a challenge.
The official guidance involves using the specific commit hash for the module you want, like this: