ci: Add PR test for running goreleaser snapshot #218
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
caitlinelfring
force-pushed
the
goreleaser-pr-action
branch
from
2c212e3 to
944c246
Compare
caitlinelfring
changed the title
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
CI
What is the current behavior? (You can also link to an open issue here)
There is no CI check to validate changes to goreleaser.
What is the new behavior (if this is a feature change)?
We now run
goreleaser release --snapshot --rm-diston PRs when related files are changed.Does this PR introduce a breaking change? (What changes might users need to make due to this PR?)
No
Other information:
This is related to possible breaking changes to releases in #216 that would not be shown during CI