actions/setup-go
actions/setup-go
1
0
Fork 0
mirror of https://code.forgejo.org/actions/setup-go.git synced 2024-12-25 22:42:22 -05:00
Code Issues Projects Releases Packages Wiki Activity

docs: add tiny reference for the .tool-versions

Browse source 
See https://github.com/actions/setup-go/pull/402
This commit is contained in:
Victor Martinez 2023-08-15 14:26:05 +02:00
parent fde5dd24bd
commit 721bdf3e4e
No known key found for this signature in database
GPG key ID: 419518ED0DA3CBCF
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
README.md
View file

@ -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 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