-
1. With no options `history` outputs all non-command non-yetibot history
1. `--include-commands` (commands are excluded by default)
1. `--commands-only`
1. `--include-yetibot` (yetibot is excluded …
-
Yetibot's output can get muddled when asking it to output history because then Yetibot's own output will then also include other user's histories. To help provide a way to get history of output for sp…
devth updated
5 years ago
-
This appears to work most of the time, but at least once it didn't in one room. Need a consistent repro.
devth updated
5 years ago
-
I'll add dev docs yetibot/yetibot.github.io as I work through this.
ref: yetibot/yetibot.github.io#39 and maybe yetibot/yetibot.github.io#13
-
```
!gh repos yetibot | clj (count data)
```
```
:cop: Syntax error compiling at (form-init3120510771544454927.clj:1:113). :cop:
```
devth updated
5 years ago
-
I think this is because the hooks aren't reset after each load. It might be better to
reload all namespaces _except_ for yetibot.core, since that contains the function
that gets hooked: `handle-comman…
devth updated
5 years ago
-
-
devth updated
5 years ago
-
-
devth updated
5 years ago