ci: notify teams about calcite-components releases only#7317
Merged
Conversation
benelan
added a commit
that referenced
this pull request
Jul 20, 2023
…shot-doc * origin/main: chore: release next fix(tooltip): ensure --calcite-app-z-index-tooltip is applied (#7345) docs: add warning notice to internal storybook (#7338) chore: remove references to removed cleanup script (#7339) chore: drop Airtable syncing action (#7340) chore: release next fix(color-picker): maintains correct numbering system when entering invalid RGB value (#7327) ci: notify teams about calcite-components releases only (#7317) build(deps): Bump rollup from 2.77.1 to 3.26.0 (#7264) build(deps): Bump eslint-plugin-jsdoc from 46.4.3 to 46.4.4 (#7329) build(deps): Bump semver and @types/semver (#7309)
benelan
added a commit
that referenced
this pull request
Aug 5, 2023
**Related Issue:** #7317 ## Summary I thought I had removed this original teams notification action but it must have been added back while I was fixing merge conflicts. This one caused two notifications, one for each package. The one added in the PR linked above will only notify about CC releases.
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
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.
Original PRs: #3771 #5512
Summary
Adding back the Teams release notification action. I had to refactor it after the monorepo transition so it wouldn't spam the channel with release notifications for all of the packages.
We can make additional steps for different packages that go to different channels at some point. For example, a
design-tokensrelease notification to "Get Help - Design and FIGMA"