-
Notifications
You must be signed in to change notification settings - Fork 23
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
Add "trigger" support to respond to non-command text #117
Labels
enhancement
New feature or request
needs-docs
This issue will need addition or changes to documentation
Milestone
Comments
clockworksoul
changed the title
Add "trigger" support to do things in response to non-command text
Add "trigger" support, to do things in response to non-command text
Oct 13, 2021
clockworksoul
changed the title
Add "trigger" support, to do things in response to non-command text
Add "trigger" support to respond to non-command text
Oct 13, 2021
@clockworksoul Given the above commit can this be closed? Or was there follow up work needed? |
theothertomelliott
added
the
needs-docs
This issue will need addition or changes to documentation
label
Jun 6, 2022
As discussed "in-person" this will need documenting. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
New feature or request
needs-docs
This issue will need addition or changes to documentation
Currently Gort only responds to explicit commands, formatted like structured commands. There should be some kind of ability to respond to non-command text, sort of like Slack "triggers" (but not like Cog "triggers", which are very different).
Triggers would be configured with a pattern to match and a command, so when Gort sees text matching the defined pattern, it executes the command.
Open question: How will it behave wrt to trigger text + command inputs?
What if a command also matches a trigger? Which takes precedence?
What about timed triggers (maybe use cron definitions)?
The text was updated successfully, but these errors were encountered: