Slack: Option to disable /deployment for organizations

[oliikit]

Hello!

I noticed that you all released the deployments command yesterday (https://github.com/integrations/slack/pull/698). First off, congratulations! I'm sure this will be useful to some folks. But is there a way to disable it for organizations? From reading the blog post, it does not appear so.

It would be useful as an org owner to have very granular controls on this setting as most of my organizations already have established CI/CD pipelines and Slack is an untrusted environment.

If there was a way for us to opt into a certain version of the GitHub app, that would be helpful - but then we wouldn't get future updates. So I'm unsure what the best way to approach this would be. Perhaps there could be a master setting in Slack and have only organization owners enable/disable this feature? And if that setting is ever changed, it should fire off an alert.

I'd appreciate your thoughts. 🙇‍♂️

[welcome[bot]]

Thanks for opening this issue! If you would like to help implement an improvement, read more about contributing and consider submitting a pull request.

[dennissivia]

Hi @oliikit 👋 , thanks for asking this.

Reading your question:

But is there a way to disable it for organizations?

Did you try using unsubscribe (analogous to the configure docs)?

The command would be: /github unsubscribe your-org deployments

[oliikit]

Hey, @scepticulous! Yes - but would that have to be on a per-slack channel, per-repo based as with the other commands? Also, would _everyone_ with GitHub access be able to enable/disable this feature?

The worry here is that while organization owners disable it, a repo admin may enable it. If we don't have notification about it or have a way to audit what permissions each repo/channel has, we wouldn't know.

[dennissivia]

Thanks for clarifying.
This functionality doesn't currently exist and I understand the motivation. I am tagging this as a "feature request" since this is a new concern. Thanks for bringing this up.

[oliikit]

Awesome, thank you so much! Let me know if you need any further clarification or help scoping it out.

[jez]

Chiming in that this feature would be much appreciated.

With the newly announced Scheduled Reminders feature, I get a nag notification every day to upgrade, but I can't upgrade my organization because our Slack is a public community, but our project only has a handful of people who can write to it.

This has also made me realize that the same thing applies to Issues and Pull Requests—the Slack app requires write access for those too, when all i really want is pull request reminders.