I updated the bot to add random numbers / digits to the repo name. And I gave it DB read access to screen incoming webhook payloads -- it checks that they are for an assessment tracker entry which the bot can access. Together, these improvements fix all potential bot conflicts between development & production and between local testing runs.
I updated the bot to add random numbers / digits to the repo name. And I gave it DB read access to screen incoming webhook payloads -- it checks that they are for an assessment tracker entry which the bot can access. Together, these improvements fix all potential bot conflicts between development & production and between local testing runs.