Skip to content
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

[NEW] Internal hubot support for Direct Messages and Private Groups #8933

Merged

Conversation

ramrami
Copy link
Contributor

@ramrami ramrami commented Nov 23, 2017

@RocketChat/core

Before

Internal hubot only responded to public rooms (room.t = 'c')

After

Internal hubot respond to the enabled room types ( 'c' or 'd' or 'p')

Edit
The bot respond in private groups only if it's added to that group.

Closes #7550 (maybe 5191 also)

@reetp
Copy link

reetp commented Dec 13, 2017

Nice if this could make it in to 60 :-)

@slyk
Copy link

slyk commented Jan 9, 2018

I would like people to DM to my hubot.
Internal is working ok on channels, but that creates scrapyard of messages, that needed only for person who talks to hubot.

Was trying to edit snap files to fast get this feature, but can't do this because of protection :(


hubot-rocketchat adapter could use DM, but I wanted to use internal.

How could we add this to release?

@reetp
Copy link

reetp commented Jan 19, 2018

@ramrami is there any chance you could look at this ?
It would be really good to have it fixed.

@ramrami
Copy link
Contributor Author

ramrami commented Jan 19, 2018

@reetp It's ready to be merged. All we need is a review from core team members.

@reetp
Copy link

reetp commented Jan 21, 2018

@rodrigok can one of the devs look at this?

A fix and PR has been languishing here for some while for a bug that has been open for ages. I don't understand why it has been ignored so long.

Thanks.

@geekgonecrazy
Copy link
Contributor

Sorry guys some how this slipped by.

@geekgonecrazy geekgonecrazy added this to the 0.62.0 milestone Feb 5, 2018
@reetp
Copy link

reetp commented Feb 5, 2018

Thanks Aaron :-)

@reetp
Copy link

reetp commented Feb 5, 2018

As far as I can see it fixes:
#3132
#5191
#7550

@reetp
Copy link

reetp commented Feb 15, 2018

@ramrami is there anything that needs to be done so we can see this in the 0.62 release ?

@ramrami
Copy link
Contributor Author

ramrami commented Feb 15, 2018

@reetp It's already approved by @geekgonecrazy, and it has been added to the 0.62.0 milestone. I'm not part of the team, so I can't merge it ^^

@geekgonecrazy
Copy link
Contributor

We'll began merging PR's for 0.62.0 I believe this next week. No worries, I don't see any reason this won't land

@rodrigok rodrigok merged commit 99928a1 into RocketChat:develop Feb 17, 2018
@rodrigok rodrigok mentioned this pull request Feb 28, 2018
@vaggeliskls
Copy link

vaggeliskls commented Mar 14, 2018

Iam using 0.62.2 version of rocketchat on Centos with custom installation.
I have update the Enable for Public Channels, Enable for Direct Messages and Enable for Private Channels to true. Iam trying to do an bot help command but no response on private channels. On direct and public channels work perfectly. Any idea ?
P.S I had done this fix before it was merged and worked perfectly for all channels

Any idea ?
image

@ramrami
Copy link
Contributor Author

ramrami commented Mar 14, 2018

@vaggeliskls Did you invite the bot to the private channel ?

@vaggeliskls
Copy link

vaggeliskls commented Mar 14, 2018

Ok. Thanks you very much. I run /invite @rocket.cat and then @rocket.cat help and it worked. Fast response and really useful community.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants