This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of hubot-slack.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Hello lovely humans,
hubot-slack just published its new version 4.0.3.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of hubot-slack. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
GitHub Release
robot.messageRoom
now accepts room names, not just IDs. Because sometimes all you have is a name. (#346)as_user=true
by default now.The new version differs by 169 commits .
971c505
4.0.3
b199250
Fix #350
a56d10e
Merge pull request #356 from slackhq/correct-outgoing-messages
41281a4
fixed tests
4eb7de4
correct outgoing messages posts - fixes #236
825de6b
Merge pull request #346 from mdelagrange/accept-room-names
3ebbfd0
treat any room with an uppercase letter as a channel id
cfac95a
leave existing tests alone
d019928
accept room names for robot.messageRoom
46aca19
Merge pull request #337 from slackhq/default_as_user_true
bc2e3d9
And finally tests on the actual feature under development
894f694
The fault was in the test
e5959e7
Well, we have one new passing and one failing test.
640b5ad
Well, at least the tests won't crash now.
e3b62b3
Ignore messages sent by us, regardless of how it was sent, and if as_user was set
There are 169 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade