Skip to content
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

fix: users now can start again after a /stop command #113

Conversation

gentlementlegen
Copy link
Member

@gentlementlegen gentlementlegen commented Dec 27, 2024

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.

@gentlementlegen gentlementlegen marked this pull request as ready for review December 27, 2024 07:45
@gentlementlegen gentlementlegen merged commit d80c772 into ubiquity-os-marketplace:development Dec 28, 2024
2 checks passed
@gentlementlegen gentlementlegen deleted the fix/start-again branch December 28, 2024 23:15
@ubiquity-os-beta ubiquity-os-beta bot mentioned this pull request Dec 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

/stop can start again
2 participants