Add Slack support - report deployed pull-requests to a Slack channel #11
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.
Users can configure a Slack hook for prout by creating a new Slack 'Incoming Webhook':
https://your-domain.slack.com/services/new/incoming-webhook
...this will get you a 'Webhook URL', which looks something like this:
https://hooks.slack.com/services/T05FTQF9H/B012N1Y2Y/p9VyRC1ZlTqNGuu
...stick that url into a GitHub webhook for your repo as the 'Payload URL':
https://github.com/my-org/my-repo/settings/hooks/new
...and then disable the hook in GitHub! You don't actually want to send GitHub events to the hook - this is just a place to store the private url where Prout can find it. Note that prout needs repo-admin access in order to read the hook data!
This comes from @tackley's request for Ophan - he wants a way for users who don't have GitHub access to see features as they're released. Slack has a lower bar to entry for some of our users...
cc @tackley @philwills