Add multi-module support to project infrastructure #71
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.
Projects may contain multiple Go modules in subfolders of the repository. In order to support checks on these modules,
it's necessary to configure the commands to run from their path. This is passed to the task via the GO_MODULE_PATH
environment variable. If this variable is not defined, the default root module path is used as default, preserving the
previous task behavior.
The workflows use a job matrix to allow easy configuration for any number of module paths and a dedicated parallel job
for each module.
Although this particular repository does not contain multiple modules, at the moment, and though there may be no plans to
add them at the moment, these are intended to be general-purpose assets that can be applied to any project. Since other
projects do contain multiple modules, the capability is necessary and this project inherits such.