You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a PR is merged with a skip-release label, a release should not be made.
Use Case
If a PR does not add any functionality to the actual module, e.g. a README typo fix, then there should be a way to skip the release. Repos using this template should have this ability.
Describe Ideal Solution
At first I believed that simply setting exclude-labels in .github/auto-release.yaml will enable this. However that only skips the release from being drafted. A release will still be made because of the publish action input.
The actual solution probably involves detecting the labels in the PR and programatically setting publish based on that, within the auto-release GitHub Actions workflow.
Alternatives Considered
N/A
Additional Context
N/A
The text was updated successfully, but these errors were encountered:
Have a question? Please checkout our Slack Community or visit our Slack Archive.
Describe the Feature
The
exclude-labels
option should be included by default inauto-release.yaml
Expected Behavior
When a PR is merged with a
skip-release
label, a release should not be made.Use Case
If a PR does not add any functionality to the actual module, e.g. a README typo fix, then there should be a way to skip the release. Repos using this template should have this ability.
Describe Ideal Solution
At first I believed that simply setting
exclude-labels
in.github/auto-release.yaml
will enable this. However that only skips the release from being drafted. A release will still be made because of thepublish
action input.The actual solution probably involves detecting the labels in the PR and programatically setting
publish
based on that, within theauto-release
GitHub Actions workflow.Alternatives Considered
N/A
Additional Context
N/A
The text was updated successfully, but these errors were encountered: