Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TAPS-436] Move notifications to new channel #374

Merged
merged 1 commit into from
Jan 9, 2025

Conversation

pudek357
Copy link
Contributor

@pudek357 pudek357 commented Jan 9, 2025

TAPS-436

Development checks

  • Add changeset according to guidelines (if needed)
PR commands

List of available commands:

  • @toptal-anvil ping reviewers - Ping teams for review

@pudek357 pudek357 self-assigned this Jan 9, 2025
@pudek357 pudek357 requested a review from a team as a code owner January 9, 2025 08:01
Copy link

changeset-bot bot commented Jan 9, 2025

⚠️ No Changeset found

Latest commit: ea0cd45

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@pudek357 pudek357 merged commit 05826b1 into master Jan 9, 2025
4 of 5 checks passed
@pudek357 pudek357 deleted the TAPS-436-route-notifications-to-new-channel branch January 9, 2025 10:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants