It would be great to be able to filter activity alerts based on a list of branches, similar to what's available in the legacy app (the setting was labeled: 'Branch | Optional branch (or comma-separated branches) to filter on.').
From the configuration notes it appears we can only do 'default branch', 'all', or 'none', effectively. If I'm misreading, I'd love to hear if this is possible. Many thanks.
elliottyates
All 111 comments
This was critical to my company's usage. We had separate channels for checkin notices (pushes to develop) vs. releases (pushes to master) so that managerial staff could be aware of production deployment.
signe
on 13 Mar 2018
Agreed, we're finding the integration unusable in our Slack #github channel without only specifying specific branches (e.g.: only master, dev, staging) and ignoring the rest. Becomes amazingly spammy otherwise. This was supported in the legacy app so it would be lovely to have it included here.
nickbouton
on 14 Mar 2018
We are missing this in our organization as well.
Need the ability to subscribe to one or multiple branches in a repository.
kling90
on 21 Mar 2018
Indeed, especially if you are following the git-flow model, this is highly needed.
memphis88
on 22 Mar 2018
yes, it's important to have separate notifications for separate branches. The only solution for now is using custom script to accept hooks from github and send messages to slack.
pmartini
on 23 Mar 2018
+1 for importance for us too. We have to uninstall this because we need notifications for multiple stable branches, but certainly not ALL branches in the repo.
teeohhem
on 23 Mar 2018
Great suggestion - we can't migrate from the legacy app until this is implemented.
quattromatt
on 2 Apr 2018
A big +1 here as well. The existing syntax, as found at https://github.com/integrations/slack#configuration, could already accommodate filtering for at least one specific branch. Right now it's possible to do:
/github subscribe alice/some-repo commits:all
What follows the colon could be the name of any specific branch, e.g.
/github subscribe alice/some-repo commits:some-topic-branch
In any case, this is one more feature missing from the new app that was present in the old one. I'm loving the convenience of having a /github subscribe slash command (have wanted this for years!) but I'm afraid it's coming at a pretty steep cost. Thanks for considering.
cbeams
on 9 Apr 2018
also would be nice if it supported wildcards, e.g.
/github subscribe alice/some-repo commits:release*
We create release branches for each release. These notifications would be nice for our product team that is very concerned with activity only related to release branch.
jaywclark
on 12 Apr 2018
Along the same lines, being able to limit the type of activities that alert would be nice (in my case I only want to know when a PR is opened, nothing else).
WolverineFan
on 30 May 2018
+1
landsman
on 8 Jun 2018
+1
jurgisrudaks
on 15 Jun 2018
Any timeline on this? Pretty essential in order to EOL the legacy app.
slavingia
on 19 Jun 2018
Yes. +1
AndyUrquijo
on 22 Jun 2018
Please! +1
AdamDenoon
on 23 Jun 2018
+1
jasonmoore2k
on 13 Jul 2018
along the line, it would be nice to be able to filter deployments by branch, since we use feature branches for QA's
Saayaman
on 16 Jul 2018
+1
jonysk
on 22 Jul 2018
::::Need to subscribe github-url for a specific feature branch::::
I am using Slack.
I have added GutHub App.
I have already subscribed my github project.
I am able to get all the commits info for master branch.
Requirement:
I want notifications regarding commits,etc. only for a specific feature branch.
Please help here.
mayank-mahajan-guavus
on 27 Jul 2018
+1
jmymy
on 31 Jul 2018
+1
diescake
on 3 Aug 2018
+1
davingreen
on 3 Aug 2018
+1
mscanzillo
on 6 Aug 2018
+1. just posting to bring this up again.
deeTEEcee
on 2 Oct 2018
I tried the above solution with commits:
bvergara87
on 25 Oct 2018
@bvergara87
This
/github subscribe alice/some-repo commits:some-topic-branch
was just a suggestion.
keckelt
on 26 Oct 2018
The only two currently available commit subscribe options are:
Subscribe to default branch commits:
/github subscribe alice/some-repo commits
Subscribe to all branches commits:
/github subscribe alice/some-repo commits:all
Would love to:
Subscribe to named branch commits:
/github subscribe alice/some-repo commits:branch-name
campaignupgrade
on 1 Nov 2018
I feel like this is pretty critical functionality as well! Otherwise this integration has a pretty narrow use case. +1
KOGI
on 2 Nov 2018
I am commenting as I would seriously appreciate/need this.
hjelmeir
on 24 Nov 2018
As a workaround I compare the hashes returned by git ls-remote and post a Message to Slack via the API if the hash changes.
keckelt
on 27 Nov 2018
@keckelt how is that implemented? locally?
campaignupgrade
on 7 Dec 2018
@slamorte Yes. I utilized an old Raspberry Pi 1 to run a python script every few minutes.
keckelt
on 10 Dec 2018
simply commenting to say that this feature is essential to keeping this integration in our workflow
blakerutledge
on 13 Dec 2018
+1 to the above comment. GitLab's integration is very good, so you could "borrow" a few of their approaches!
thejoshsmith
on 20 Dec 2018
I have nothing to add except "this."
This was the first thing I looked for after installing GitHub for Slack. So it was quite disappointing to find it didn't exist.
dmm-pete
on 20 Dec 2018
Note to peeps who want this - please add a +1 reaction to the initial post at the top of this issue. Adding additional ‘me too’ and +1 comments that don’t add additional information just clutter up the thread, and make more noise both for those who might be able to implement this and those who are subscribed for updates. Thanks!
tdmalone
on 23 Dec 2018
Hey, any update on this feature?
bombillazo
on 19 Feb 2019
wow. this is wish for all users
samslow
on 23 Mar 2019
Still waiting this features
ImTung
on 8 Apr 2019
Any updates?
hacker-DOM
on 24 May 2019
Is there any plan to implement this feature ?
ykumar-rb
on 10 Jun 2019
+1
phagunbaya
on 27 Jun 2019
yes, please, this would be so appreciated
chmccc
on 10 Jul 2019
Hey everybody.
We noticed, that the demand for this feature and put it onto our list for future enhancements.
We don't have a concrete timeline for this, but I wanted to quickly let everybody know, that we are aware of this feature request.
dennissivia
on 5 Aug 2019
+1
rocktavious
on 20 Aug 2019
After going through this thread again, I have a few concrete questions to understand the details of the most requested subset of features.
Feedback
+1 to the above comment. GitLab's integration is very good, so you could "borrow" a few of their approaches!
@thejoshsmith could be more specific? Is there a specific feature you are referring? If that is the case it would be great, if you opened an issue for the most desired feature, so that we can see if there is an easy way to implement it, depending on the existing demand.
Feature request summary
Single branch
It would be easiest to allow any custom branch name like suggested above:
/github subscribe org/repo commits:dev. And this would only subscribe to that branch.
But I doubt that this would really satisfy the described use case. (what do you think @campaignupgrade, @cbeams ? since you suggested that syntax)
Multiple branches
To me, it sounds, as if this feature requires "multiple" OR combined branches.
The example that @nickbouton gave above: "master, dev, staging"
Wildards
Right now, I think wildcards are an independent feature request. I really like the idea, but I think we have to consider that in a separate issue.
@jaywclark if you (or anybody else) still considers wildcard (branch-)filters something they would use in their production setup today, please feel free to open an issue to start getting feedback and input.
Opinions
Please vote this issue with 🚀 if you think shipping a single-branch subscription (instead of master). Otherwise, I will assume, that my assumption, that multiple branches are a required minimal feature-set is correct.
cc @integrations/integrations-reviewers
dennissivia
on 20 Aug 2019
I agree that multiple branches is preferred, at least for our use cases (we have multiple integration branches that it's nice to see commits for, but don't want commit notifications on feature branches). Thanks @scepticulous.
elliottyates
on 20 Aug 2019
We would see benefit in our specific use cases in being able to subscribe to a specific branch (including a feature branch) within a given channel. i.e.: those focused on a specific project/feature implementation.
Wildcards/allowing multiple branches for a given channel subscription would satisfy other use cases - i.e.: teams/resources looking for notification on commits or pulls on specific items/branches they are assigned to.
NeilWacekUMV
on 20 Aug 2019
/github subscribe github-account/repo pulls:master ?
This is required. Looking forward to this improvement. Following .....
Thanks
GaddMaster
on 22 Aug 2019
Is there any eta for this feature been added ?
GaddMaster
on 22 Aug 2019
Is there any eta for this feature been added?
No, there is no ETA yet. I need to wrap up some other tasks first, but this issue is one of the top priorities for improving subscriptions. I will follow up when I have more details.
dennissivia
on 23 Aug 2019
@scepticulous Hows things. Any progress with this feature.
Daniel
GaddMaster
on 12 Sep 2019
@scepticulous , hi , Dennis, any updates? would love to have it
Thank you,
Oleksandr
OleksandrMalinin
on 30 Oct 2019
I know this is available via Github enterprise server plugin on slack
ark02
on 9 Nov 2019
@dennissivia : was thinking about your post earlier. The problem with using branch as the 2nd half of the keyword directive, commits:[branch] is that the subscription is only added for that one feature.
Someone would have to explicitly name all features:
/github subscribe org/repo commits:[branch_name]
/github subscribe org/repo issues:[branch_name]
/github subscribe org/repo pulls:[branch_name]
/github subscribe org/repo statuses:[branch_name]
/github subscribe org/repo deployments:[branch_name]
From a usability perspective, a user adding a subscription for a branch would likely expect all default subscription "features" (issues, pulls, commits, etc.), as if they had specified the default branch, i.e. /github subscribe org/repo.
From a syntax standpoint, this might be equivalent to any of the following:
/github subscribe org/repo branch:[branch_name]
/github subscribe org/repo:[branch_name]
And with a specific feature, either syntax:
/github subscribe org/repo branch:[branch_name] commits
/github subscribe org/repo commits:[branch_name]
The explicit branch:[branch_name] keyword might work better for following reasons:
- easy to test whether
branch:is provided - is clear with intent (documentation and command help output)
- output from
/github subscribe listwould be obvious with intent for notes or copy/paste
neurogenesis
on 15 Nov 2019
👋 Hi folks! A couple updates here.
Priorities have shifted a bit and progress on this work stream has slowed down. Sorry for the delay in responses. We will update as we pick up steam again. Thanks for the follow ups on the feedback requests, we are considering all of this as we re-prioritize.
In addition, @dennissivia is no longer working on this project. Feel free to ping me moving forward. 🙇
philipbremer
on 15 Nov 2019
Latecomer to the party here... We would also love to be able to say something along the lines of:
/github subscribe org/repo commits:all-*/wip/*
to exclude user/wip/thingy branches that are not yet worthy of wider-scoped notifications for all.
berendo
on 30 Dec 2019
+1
federicoaaguirre
on 8 Jan 2020
Would love to have this feature as we use branches that are connected to environments: production, acceptation, etc.
gregorybolkenstijn
on 14 Jan 2020
This feature is very handy, Would make our workflow a lot easier.
on another note Zapier does the job.
MarwanAlGalaly
on 21 Jan 2020
Would love this feature as well, it's quite critical for this plugin to be really useful
temidevops
on 26 Feb 2020
@MarwanAlGalaly, do you know if you can set up a zap in zapier with wildcard mathcing? i.e. prd-*
rggallison
on 13 Mar 2020
Hey there! Just another up for this important feature. The issue has been opened more than 2 years ago, any progress here? Being able to use any of the current feature on a specific branch would be very interesting for our projects. Otherwise, it makes the integration not really useful as you either have to cut down on a lot of notifications, or you're overwhelmed :/
Danetag
on 17 Apr 2020
This would be much appreciated, for many use cases--one in particular is git flow, which means you rarely push to the master. What's the point of the integration in that case?
lindseybradford
on 21 Apr 2020
+1
JSpiner
on 24 Apr 2020
+1
juanpprieto
on 25 Apr 2020
+1
rocktavious
on 29 Apr 2020
+1
kowsar89
on 11 May 2020
Is it possible to filter so my channel only gets notifications from a given repository but only for specific users?
My team works on a an open-source repository and we want to receive Slack notifications in our team Slack channel but only for PR raised by one of the team members (not the whole world!).
hugueskamba
on 14 May 2020
+1
noreika
on 19 May 2020
Hey everyone! Is there any updates on this issue?
pliniogsnascimento
on 29 May 2020
It's been over 2 years since this issue was opened and there's a clear desire for the feature from the user base. It would be nice to hear _some_ sort of update from the team 😃
@dennissivia @IAmHughes @gimenete @wilhelmklopp
KOGI
on 1 Jun 2020
+1
junhoyeo
on 8 Jun 2020
+1 Any news about this issue?
ArthurLDS
on 8 Jun 2020
+1
gutomaia
on 23 Jun 2020
+1
h4ste
on 29 Jun 2020
Sorry, but after 2 years still no update?
dyaskur
on 1 Jul 2020
We would also love this feature!
axooh
on 6 Jul 2020
+1
cainj
on 10 Jul 2020
+1
andresovela
on 14 Jul 2020
+1
colinricardo
on 21 Jul 2020
+1 .. guessing no progress though?
konradstrachan
on 4 Aug 2020
+1 Seems like a basic requirement, also handled by the API, but its been more than 2 years
nicholasmparker
on 7 Aug 2020
plz add this, much needed :)
adrach
on 7 Aug 2020
+1 for the feature.
anton-mesnyankin
on 14 Aug 2020
+1
joeydong
on 14 Aug 2020
+1
exception
on 19 Aug 2020
+1 ... I would love to see this being implemented
smartoryu
on 20 Aug 2020
+1
leac87
on 20 Aug 2020
Was baffled when enabling the GitHub integration in slack that this wasn't possible.
SneWs
on 2 Sep 2020
Why this feature is not there yet. Are you even using GitHub slack integration in your org at all?
ssharma1logitech
on 4 Sep 2020
+1
alexan059
on 8 Sep 2020
+1 It's already been 2+ years since ticket was oppedn
dionedomingo
on 9 Sep 2020
This ticket has been open for 2 years now? is this that complicated a task?
iamjonbradley
on 14 Sep 2020
Adding my name to the ever-growing list of people who would really appreciate this feature.
nheape
on 18 Sep 2020
Adding my name to the ever-growing list of people who would really appreciate this feature.
And my axe!
Give it to us, this precious feature please!
T-Coded
on 18 Sep 2020
Danetag
on 18 Sep 2020
Plus One
wazcov
on 21 Sep 2020
Bring it back please.
adrian-klang
on 5 Oct 2020
+1
henrimrsv
on 6 Oct 2020
This feature will greatly help the Linux Foundation Public Health Landscape: https://landscape.lfph.io
There is a very strong request from people to be notified when the Landscape is updated.
The Landscape is deployed to Netlify on commit.
The broader public should be notified only on merge into master,
not on build of working branches during the preparation of the updates.
T. E. Shaw, t.e.[email protected]
dahoum
on 9 Oct 2020
+1
Diiru
on 10 Oct 2020
+1
victordamatta
on 13 Oct 2020
Please do a 👍 on the initial comment. No need to +1.
xbglowx
on 13 Oct 2020
I understand this project is sort of in maintanence mode now, but lots of people including myself would love to see this feature added. If no one is working on this feature, I would like to try and implement it and submit a PR. I'm thinking of adding an additional field in the subscription settings. Something like:
+branch:"branch_name1" +branch:"branch_name2"
This should work similarly to how label-based filtering is working now. This would also make it easy to filter notifications for other types of events based on branches, as @Saayaman suggested earlier in this thread.
along the line, it would be nice to be able to filter
deploymentsby branch, since we use feature branches for QA's
I want to hear from the project owners if they hopefully approve of this.
j30ng
on 18 Oct 2020
I'm not sure if it's appropriate to post an alternative solution here, but we built a tool for this exact use case of filtering Slack notifications by branch. Our tool (1) lets you create filtered views of your GitHub events (e.g., by branch) and (2) connect those views to Slack channels. Check out this 3-min demo video to understand how it works. If you go to our homepage and "Request early access", I'll hook you up. We'd love your feedback as we're iterating rapidly.
danielfschmidt
on 21 Jan 2021
This feature requests is from 2018 and it seems that at least 470 people would like it...
GitHub ? Any news ?
xakraz
on 28 Jan 2021
This feature requests is from 2018 and it seems that at least 470 people would like it...
Make that 479 people.
abunch
on 14 Feb 2021
github belongs to microsoft, now...
and microsoft has teams...
sooo... I guess there won't be much effort on slack integration
bannier
on 15 Feb 2021
Such a shame a piece of software used by many not getting tended at all. I wish they just announce that this project will not be maintained anymore. I don't want to keep receiving notification mails on this thread.
j30ng
on 15 Feb 2021
this is now /github subscribe alice/some-repo commits:*
Dan-Moss
on 16 Apr 2021
Related issues
axos88
·
5Comments
smoke
·
5Comments
flybd5
·
5Comments
atopiler
·
3Comments
chaim1221
·
4Comments
Most helpful comment
A big +1 here as well. The existing syntax, as found at https://github.com/integrations/slack#configuration, could already accommodate filtering for at least one specific branch. Right now it's possible to do:
What follows the colon could be the name of any specific branch, e.g.
In any case, this is one more feature missing from the new app that was present in the old one. I'm loving the convenience of having a
/github subscribeslash command (have wanted this for years!) but I'm afraid it's coming at a pretty steep cost. Thanks for considering.