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
github: add Github Actions workflow for tests; support in vet.sh #4005
Conversation
|
||
# Run the vet checks. | ||
- name: vet | ||
run: ./vet.sh -install && ./vet.sh |
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.
This workflow runs vet (gofmt/golint...) twice now.
Should we move the proto regen part out to it's own job?
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.
I was thinking as a follow-up change I would add an option to vet to make it ONLY run the proto checks. WDYT?
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.
SG.
Do the proto checks need anything from vet.sh? Or just move it to a separate .sh
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.
They both need the checks up front to make sure your branch is clean & revert any changes it makes to it.
I would probably keep them together to support the "running offline" use-case better. VET_ONLY_PROTO=1
or something?
No description provided.