Hi <!channel>, I have a quick check to run by you guys. We are ready to do our first release of nfcore/mcmicro (dont mind it is called 2.0.0) I am looking at the checklist in the (nf-co.re)[nf-co.re/docs/developing/pipelines/release-procedure] to make sure we check all the boxes. Is there anything else we should have in mind?

Just to let you know, you alerted and asked all 14,434 people on this channel to run your quick check 😅 ..Which is probably more of an issue for allowing everyone to tag channel on these really big channels..

That was loud mate. Other than that, not much, the checklist is very comprehensive. The real to-dos will surface during release review, if you haven't done it yet. Next time please send the message without a tag, we will see it next morning.

..Which is probably more of an issue for allowing everyone to tag channel on these really big channels..

Ask Slack, please 🙏🏻 (been wanting that feature for many years)

Getting a bit off-topic, but trying to be solution oriented here.. I mean I've had pretty good success with configuring Slack workspaces using the channel specific permissions for here/channel mentions, combined with role specific tagging permissipns.. You should be able to e.g disable channel-tagging for this channel for others than admins etc..

we are on a slack Pro plan, so we can only limit things in #CE6P95170 (which is our #C09V1G966U8):

Makes sense @mashehu 👍 Looks like the ones I've been maintaining are on Business+, which allows e.g.: • Channel specific limits for channel/here-tags • Warnings for channel/here-tags • Role specific enabling of channel/here-tags I'm sure that Pro makes most sense for you, and did not know that these specific features were in the Business+ plans..