-
Notifications
You must be signed in to change notification settings - Fork 6
feat(issue 39): quality enforcement pipeline #42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…t schema changes are on main
.github/workflows/ci.yaml
Outdated
| - uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 | ||
| - uses: actions/setup-go@0c52d547c9bc32b1aa3301fd7a9cb496313a4491 | ||
| with: | ||
| go-version: '1.21' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we make this an env var so we can manage in one place?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great callout. Even better than an env var, we can just read from the go.mod directly. I saw the action for govulncheck supported a go-version-file input and it turns out setup-go does also. Updated in: 94bf6b8
No description provided.