@W-21263659: Announce to Slack if Github release was skipped#149
Merged
@W-21263659: Announce to Slack if Github release was skipped#149
Conversation
soridalac
approved these changes
Feb 13, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
With conventional commits, if you do not use a
fix:orfeat:commit message, a Github Release will not be created. Sometimes this is what we want, sometimes we just forget. If it was a mistake, it is very easy to miss that a release was not created. If a release is not created, then it will not publish tonpmeither.create-github-releaseoverrides the conventional commits check and publish (still) works after this change: https://github.com/salesforcecli/testPackageRelease/actions/runs/22002916755/job/63579740058#step:9:1@W-21263659@