This repository has been archived by the owner on Dec 7, 2023. It is now read-only.
Add github action to update go dependencies #693
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a new github action to update go dependencies and create a PR with the changes.
The action is scheduled to run daily and can also be triggered manually from the github
actions tab. It uses branch
go-deps-patch
for creating PR.Github action can't run make target
autogen
, which usesgo-in-docker
internally due tothe interactive flags. It results in error:
To keep the existing behavior of
go-in-docker
, this PR changesgo-autogen
to workoutside of container environment.
go-autogen
make target expects the code generation tools to be available in/go/bin/
. Thisisn't true when running without the docker environment created by
go-in-docker
target.To be able to run the code generation along with dependency updates on host directly, vendor
the code generation tools using the tools.go approach.
Refer https://github.com/golang/go/wiki/Modules#how-can-i-track-tool-dependencies-for-a-module
This helps avoid changing the mod file while installing the tools with go get and the need to
perform a cleanup at the end. It helps ensure that the vendored code-generation tools will always
reproduce the same results for everyone.