Slack: Ability to filter on only showing new pull requests / merges

Created on 1 Mar 2018  Â·  9Comments  Â·  Source: integrations/slack

We use the pull notifications as a backlog of what to review. Would be nice to be able to choose a finer granularity for notifications of pull requests, for example
pulls:new
pulls:merge

Either that or being able to choose updating the color of merged PRs to purple ones instead of receiving a new notification.

good first issue subscription feature

Most helpful comment

Our team would like a pulls:merge option. We treat merges to master as mini-releases and want a separate channel just for those.

All 9 comments

510 appeared to be what I was looking for, but it was closed as a dup of this issue. Specifically, I would like to see all activity related to a PR appear as thread replies to that PR's thread. If that doesn't sound like what this issue is supposed to solve, please let me know. I will create a new issue.

Is this still relevant? If so, just comment with any updates and we'll leave it open. Otherwise, if there is no further activity, it will be closed.

This is still relevant. I like the solution from #510 with threading.

Our team would like a pulls:merge option. We treat merges to master as mini-releases and want a separate channel just for those.

The solution for this mentioned in #510 sounds like it would be amazing and keep our channel way cleaner.

@gordontucker Have you looked into doing this using a custom GitHub Workflow? I created a starter Action that handles posting to Slack – https://github.com/pullreminders/slack-action – all you'd have to do is create a workflow that subscribes to the specific events you want notifications for.

It could be nice to add some sort of filter to a tag, so for a large codebase, a PR could go to different channels depending on their tags.

Hey everybody 👋

I think implementing arguments for pull as suggested by @larsjoakimgrahn sounds like a feasible solution to the described problem.
I suggest the following to options: pulls:opened and pulls:closed, so that the argument matches the event action.

Please let me know if this would work for all of your use-cases. If not, please let me know.

Closing in favor of #519, since it asks for the same features.
Please check out that other issue and if your use-case is not covered there, consider commenting there or creating a dedicated issue, if necessary.

Was this page helpful?
0 / 5 - 0 ratings