mirror of
https://github.com/actions/setup-go
synced 2024-11-14 17:42:40 +00:00
docs: add tiny reference for the .tool-versions
See https://github.com/actions/setup-go/pull/402
This commit is contained in:
parent
fde5dd24bd
commit
721bdf3e4e
1 changed files with 2 additions and 2 deletions
|
@ -181,9 +181,9 @@ If both the `go-version` and the `go-version-file` inputs are provided then the
|
||||||
|
|
||||||
If the file contains only major and minor (e.g. 1.18) tags, the action will search for the latest available patch version sequentially in the runner's directory with the cached tools, in the [version-manifest.json](https://github.com/actions/go-versions/blob/main/versions-manifest.json) file or at the go servers.
|
If the file contains only major and minor (e.g. 1.18) tags, the action will search for the latest available patch version sequentially in the runner's directory with the cached tools, in the [version-manifest.json](https://github.com/actions/go-versions/blob/main/versions-manifest.json) file or at the go servers.
|
||||||
|
|
||||||
### If the go.mod file
|
### If the go.mod or .tool-versions files
|
||||||
|
|
||||||
The `go-version-file` input accepts a path to a `go.mod` file or a `go.work` file that contains the version of Go to be used by a project. As the `go.mod` file contains only major and minor (e.g. 1.18) tags, the action will follow the above-mentioned approach.
|
The `go-version-file` input accepts a path to a `go.mod` file, `.tool-versions` file or a `go.work` file that contains the version of Go to be used by a project. As the `go.mod` file contains only major and minor (e.g. 1.18) tags, the action will follow the above-mentioned approach.
|
||||||
|
|
||||||
> The action will search for the `go.mod` file relative to the repository root
|
> The action will search for the `go.mod` file relative to the repository root
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue