go-gitver/examples/basic
AJ ONeal 3409d5f2e4 update examples 2020-10-12 14:46:35 -06:00
..
tools complete transition to v2 2020-10-12 14:42:55 -06:00
README.md rename outfile xversion.go to lower init() priority, add outfile option 2019-06-21 00:01:02 -06:00
go.mod update examples 2020-10-12 14:46:35 -06:00
main.go complete transition to v2 2020-10-12 14:42:55 -06:00

README.md

Example

Prints the version or a nice message

Build

Typically the developer would perform these steps and then commit the results (go.mod, go.sum, vendor).

However, since this is an example within the project directory, that seemed a little redundant.

go mod tidy
go mod vendor

These are the instructions that someone cloning the repo might use.

go generate -mod=vendor ./...
go build -mod=vendor -o hello *.go
./hello
./hello --version

Note: If the source is distributed in a non-git tarball then version-generated.go will not be output, and whatever version info is in package main will remain as-is.

If you would prefer the build process to fail (i.e. in a CI/CD pipeline), you can set the environment variable GITVER_FAIL=true.