Currently, we are using only the one GitHub bot (https://github.com/apps/brn-bot) for testing, development, and production ENVs. This is a problem because testing and development require using smee.io as the webhook URL. This is unsuitable for production.
We need some way to specify a production bot which only uses the production webhook URL, rather than smee.io's URL.
Might require being able to specify the app ID, app key, etc in the .prod.env file and having logic in the ghbot code to correctly switch when in production.
Currently, we are using only the one GitHub bot (https://github.com/apps/brn-bot) for testing, development, and production ENVs. This is a problem because testing and development require using smee.io as the webhook URL. This is unsuitable for production.
We need some way to specify a production bot which only uses the production webhook URL, rather than smee.io's URL.
Might require being able to specify the app ID, app key, etc in the
.prod.envfile and having logic in theghbotcode to correctly switch when in production.