fix: support notification containers#68
Merged
Merged
Conversation
jweberst
approved these changes
May 27, 2026
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
erik-perri
approved these changes
May 27, 2026
michalm-st
approved these changes
May 27, 2026
Bankamah
approved these changes
May 27, 2026
Jasonej
approved these changes
May 27, 2026
jyann
approved these changes
May 29, 2026
kevinhagensjr
approved these changes
Jun 3, 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
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.
A few projects are just notifications so automation can't find container. I figure we don't want to blow this up too much as it would lead to finding wrong container, but I other projects refer to them as
websocketsso I think this is safe.