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
Slack notifications fails on private channel #623
Comments
Thanks for reporting about that. Will fix that shortly. |
The problem was AppVeyor always adding |
Ok let me know when it's available, I'll test it right away! |
Update with fix has been deployed. |
It works like a charm! |
To check, this means we need to update all channel properties to include the # where we didn't need them previously? |
Yes, correct. |
@FeodorFitsner We're still having problems with this. I'm looking at some oldish AV-project and clicked EXPORT YAML. this is the output...
the channel is What should we be doing for the channel name, please? I'm confused 😢 😊 |
Is it a public or private channel? |
OK, then in appveyor.yml it should be:
|
we had that originally and we were getting that error message. so then i added the EDIT: Note. this is a new thing. started happening a month ago? (Jan 2016?) before that, it's been running great for ages. |
What error do you get? Make sure channel name is in quotes if starts with #. |
So is this correct?
|
Correct, channel with lock sign is private. |
Awesome. so when do we add the |
"#" is added to non-private (non-padlocked) channels only. |
k. soz. |
I tried to set up Slash notification to my private channel using the following configuration (xxxxxx is my token encrypted here:
My Appveyor build show me the folloing error:
When testing the Slash api with the following URL, it works: https://slack.com/api/chat.postMessage?token=xxxxxx&channel=dev&text=hello&pretty=1 (where xxxxxx is my token without encryption).
It also works if the channel is not private.
The text was updated successfully, but these errors were encountered: