You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 28, 2023. It is now read-only.
When the bot is added to a group chat, it accepts messages from any user, when a user explicitly uses bot's name. Commands are then interpreted in the same way, as in chats with a single user.
Notifications are sent to the group chat when the bot is enabled, and a notification from Gerrit for any user in the group chat arrives.
What needs to be implemented:
Spark messages should be aware of their origin: single-user chat or group chat.
Actions should work even if the name of the bot is present.
When a new user enters/leaves the group chat, the bot needs to be aware of this.
The User type of the bot needs to distinguish between Users and Groups.
This feature will most likely change the storage format of the state.
The text was updated successfully, but these errors were encountered:
One more use-case for this: when you add the bot to a group chat, add the ability to give a custom filter for this chat.
e.g. if you are a member of a build scripts group chat, you wanna know when a commit is merged in a repo, but you don't care about CI feedback on said repo.
gferon
added a commit
to gferon/gerritbot-rs
that referenced
this issue
May 8, 2018
Behavior should be the following:
What needs to be implemented:
User
type of the bot needs to distinguish between Users and Groups.This feature will most likely change the storage format of the state.
The text was updated successfully, but these errors were encountered: