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
Is your feature request related to a problem? Please describe.
Talked to @hipstersmoothie about this on twitter, but I wanted to document it for good measure. Currently running auto canary in CI will always produce a canary, regardless of what labels are on a PR. For cases where we don't intend to ship a release (especially with documentation or dependency updates) it'd make sense to avoid generating canaries.
Describe the solution you'd like
Add a mechanism to skip releases to auto canary. It could be an explicit argument added to the canary command to check labels or some other mechanism.
Describe alternatives you've considered
We could choose not to solve this and instead push it to user land for them to decide how best to run or not run auto canary based off of whatever conditions they have. We do already have auto label which does help a bit.
The text was updated successfully, but these errors were encountered:
Would using the existing labels on a PR help with this? If documentation or dep-update labels are mapped to a not generate a release, auto canary also won’t produce one.
Can also use a —force flag to force it to create a release, or maybe a way to ignore labels supplying your own semver bump.
Is your feature request related to a problem? Please describe.
Talked to @hipstersmoothie about this on twitter, but I wanted to document it for good measure. Currently running
auto canary
in CI will always produce a canary, regardless of what labels are on a PR. For cases where we don't intend to ship a release (especially with documentation or dependency updates) it'd make sense to avoid generating canaries.Describe the solution you'd like
Add a mechanism to skip releases to
auto canary
. It could be an explicit argument added to thecanary
command to check labels or some other mechanism.Describe alternatives you've considered
We could choose not to solve this and instead push it to user land for them to decide how best to run or not run
auto canary
based off of whatever conditions they have. We do already haveauto label
which does help a bit.The text was updated successfully, but these errors were encountered: