-
Notifications
You must be signed in to change notification settings - Fork 464
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GitHub subscribe automatically unsubscribes #1086
Comments
Thanks for opening this issue! If you would like to help implement an improvement, read more about contributing and consider submitting a pull request. |
Hi @mveeprojects, thanks for reaching out to us and sorry for the inconvenience you face with the app. Can you please let us know if you still face the issue. If so please run the |
Hi, we ended up just creating a new private channel and adding the GitHub app there. Based on what we saw, this bug needs to be fixed, is this issue being worked on? |
Hi @mveeprojects , |
This is the bit doesn't work, even if you add GitHub integration again after changing a channel to private, the subscriptions do not stick. Is this going to be fixed to prevent people needing to workaround this by creating brand new private channels to continue to use GitHub integration? |
I have this same issue despite the fact that I'd added Github to a channel which was private on creation (not public > private) as every one has recommended: As you can see, I never unsubscribed from this repository but the last message confirms this bug. The Slack integration unsubscribed itself after I'd posted a test Issue on the repo, no matter what I've tried, I have not been able to receive any notifications about commits or issues for this repo. The target repo is private but has Slack integration installed with no error, GitHub is installed on Slack with no error, a new private channel is created and GitHub is added, subscribe method is called with no error, but some error is thrown at the point GitHub is actually receiving an event to echo into Slack. What's also odd is that I can interact with GitHub via Slack. If I try closing an issue, Slack-GitHub will tell me there was an error and it failed, but the Issue will indeed be closed so it did not fail. |
👋 @mveeprojects @Inventsable |
Thanks @amitkumariiit, is there any way I can send useful info or debug from my end? Anything to look out for in regards to the current Slack channel that might be the cause? Should I include |
@Inventsable you can run the |
Here you go: {
"team_id": "T2Q3C4KE3",
"team_domain": "battleaxedotco",
"user_id": "U01QR5C7N14",
"channel_id": "C01R026L2RZ",
"channel_name": "sandbox",
"text": "debug"
} |
I'm having this same problem. I noticed that for many private channels that were created further in the past, they work fine. But for newly-created private channels, none of them work. Note: These are not public channels that were made private. They were all set to private in channel creation. I believe something changed in the way channel creation works (on my work's slack server at least) sometime between February 23rd and March 17th. Every channel whose The Channel that works (Created February 23)
Channel that does not work (Created March 17)
|
Having the same issue, and idea how to solve this? |
I'm having the same problem too.
Any solution? |
@ashokirla updated the docs in #1141 that probably sheds some light on what changed to make this stop working. One line in the change to docs suggests a possible solution:
|
@nkcraddock I purged and re-installed the github app already and it did not solve the issue. |
@psinger You're right. I removed the integration from a test slack, and removed it completely from my GitHub account, reinstalled to both and the behavior is the same. I'm worried that the real situation here is that #1103 is accurate and the upgrade mentioned in #1141 is only being done to keep it from completely breaking due to slack's deprecation of the legacy workspace api. In #1131 they changed the contribution docs:
|
Yesterday, Github app said that:
and its name was changed to "GitHub (Legacy)". After upgrading Github app, everything works fine ! It reports the activities of our private repositories to the private slack channels. |
YES!! Me either!! |
When attempting to subscribe to some private repositories from slack (
/github subscribe org/repo
), we are returned a positive message from the GitHub app saying "Subscribed to x", and when running/github subscribe list
the newly subscribed to repo shows up. However, given a minute or so and running the... list
command again, the new repo has magically unsubscribed itself, it's no longer in the list.Any advice/troubleshooting/recommendations would be greatly appreciated 👍
Slack 4.10.3 (Mac)
The text was updated successfully, but these errors were encountered: