What would you like to be added? This is feature request - someone can point it as bug as well but I will not. Ask / Request 👉🏽 Implement exit and quit as standard commands with a simple confirmati...
To understand terminal capitalism, first you must understand recursion.
I understood it as enabling exit in addition to /exit. It’s honestly a reasonable request unless “exit” is already an internal keyword. I assume the presence of “/exit” in the text also somehow affects an effect on the Microslop bot misbehaving.
I don’t think it was. It was them putting the triage tag on themselves that seems to have put it into a loop, at least going by the progression of events.
The user put on the tag, the bot removes the tag, because only maintainers can put that on, and then puts on the tag, after which it removes it because someone who wasn’t a maintainer put the tag on.
I could see exit being an issue if you’re doing something in the CLI that might cause you to type that without passing it as a command (“What do you want the program to do after the task is complete?” “Exit”), but I’m not familiar enough with the program to say one way or the other.
I understood it as enabling
exitin addition to/exit. It’s honestly a reasonable request unless “exit” is already an internal keyword. I assume the presence of “/exit” in the text also somehow affects an effect on the Microslop botmisbehaving.I don’t think it was. It was them putting the triage tag on themselves that seems to have put it into a loop, at least going by the progression of events.
The user put on the tag, the bot removes the tag, because only maintainers can put that on, and then puts on the tag, after which it removes it because someone who wasn’t a maintainer put the tag on.
I could see
exitbeing an issue if you’re doing something in the CLI that might cause you to type that without passing it as a command (“What do you want the program to do after the task is complete?” “Exit”), but I’m not familiar enough with the program to say one way or the other.