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

Create a separate GitHub bot for the testing / development environment #24

Open
millerh1 opened this issue Jun 19, 2022 · 3 comments
Open
Assignees
Labels

Comments

@millerh1
Copy link
Member

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.

@millerh1 millerh1 added the ghbot label Jun 19, 2022
@millerh1 millerh1 added this to the First Beta Release (v1.0.0b) milestone Jun 19, 2022
@millerh1 millerh1 moved this to Backlog (low urgency) in Skill assessment app Jun 19, 2022
@millerh1 millerh1 moved this from Backlog (low urgency) to Todo in Skill assessment app Jun 19, 2022
@nghuixin nghuixin self-assigned this Jun 30, 2022
@millerh1 millerh1 moved this from Todo to In Progress in Skill assessment app Jul 25, 2022
@millerh1
Copy link
Member Author

millerh1 commented Sep 4, 2022

Hi @nghuixin -- do you mind if I take over this one?

@nghuixin
Copy link

nghuixin commented Sep 4, 2022 via email

@millerh1
Copy link
Member Author

millerh1 commented Sep 4, 2022

Thanks!

@millerh1 millerh1 assigned millerh1 and unassigned nghuixin Sep 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: In Progress
Development

No branches or pull requests

2 participants