fix: users now can start again after a /stop
command
#113
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #69
QA: Meniole#51
What are the changes
The bot was not behaving properly although the codebase was correct, it was in fact only working in the production version because basically the
BOT_USER_ID
was not set properly for the development` version, which I corrected in the environment settings in this repo.But reading the codebase I found that you could abuse the system by stacking
/stop
comments which would nullify bot un-assignment count and let you start again. So I changed the logic instead to check by assignment periods and determine what was the reason of un-assign: bot, user, or admin. Otherwise, logic remains unchanged.