| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Go-setup action allow specifying both a "go-version" and "go-version-file", in which case it falls back to the version-file if "go-version" is empty. This allows us to iterate over all modules, and run CI on the oldest supported Go version for each (in addition to "oldstable" and "stable"). Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
| timeout-minutes: 10 # guardrails timeout for the whole job | ||
|
|
||
| env: | ||
| GOTOOLCHAIN: local |
There was a problem hiding this comment.
Is this a request for go to NOT download another go version? If yes, why do we need it here? I mean, it may only happen if we have go.mod with go version less than specified here, which should never be the case.
Or is this something more generic, like "don't download anything" and omitting it may mask some issue?
Sorry, something went wrong.
| - atomicwriter | ||
| - capability | ||
| - mount | ||
| - mountinfo | ||
| - reexec | ||
| - sequential | ||
| - signal | ||
| - symlink | ||
| - user | ||
| - userns |
There was a problem hiding this comment.
I like the way it is used here. I don't like that we have to also list all the modules in the top-level Makefile.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Go-setup action allow specifying both a "go-version" and "go-version-file", in which case it falls back to the version-file if "go-version" is empty.
This allows us to iterate over all modules, and run CI on the oldest supported Go version for each (in addition to "oldstable" and "stable").