-
-
Notifications
You must be signed in to change notification settings - Fork 280
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
feat: allow servers and channels to be defined as components #665
feat: allow servers and channels to be defined as components #665
Conversation
@smoya fyi this pr goes to master, not release branch. Also, we release stuff from release branches, we create release candidates that are automatically published to the website. So you should have prefix FYI, I haven't looked into the proposal itself, just quickly noticed what you wrote when I saw a pop up in slack channel and thought I will give you a quick heads up. For proposals, I plan to delegate some time next week to jump into the review in spec repo |
c9023da
to
4658b28
Compare
Kudos, SonarCloud Quality Gate passed! |
This branch is now up-to-date with
cc @derberg |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/dnm
All stuff in place, reference implementation provided and will be released to release branches after this merge. /rtm |
🎉 This PR is included in version 2.3.0-2022-01-release.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Description
This PR is part of #660.
It allows both
servers
andchannels
to be defined as (and referenced from) components, meaning the following will be now valid:Related issue(s)
#660