feat: Support running GoReleaser on a Go project inside a subdirectory #45
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.
Sometimes you might be running a repository which needs to have the go projected rooted in a subdirectory (e.g. a mono-repo with code in multiple languages).
In this case, you can't just use
args
to specify a configuration file inside the sub-directory, since Go will still search for the module definition (or thevendor/
directory) in the current working directory from which GoReleaser is run - which happens to be the repository's root directory.This PR simply adds a new input (
subdir
) that allows you to specify a subdirectory under the repository root.