search

ubiquity-os / ubiquity-os-kernel

1 stars 14 forks source link

Config (dev/prod) Environment Switch #122

Open 0x4007 opened 2 days ago

0x4007 commented 2 days ago

So we need both bots to have access on marketplace.

We can have a new switch in the config that defines it's only for beta or production bot to read.

If the bot doesn't have a valid config then it shouldn't respond to any user actions, like comments and commands.

Originally posted by @0x4007 in https://github.com/ubiquity/work.ubq.fi/issues/54#issuecomment-2394988488

The problem to solve is that we can't have both bots installed normally on an org or else we have both responding to user actions and it gets noisy. We need to install both to be able to dispatch actions/events on the ubiquity-os-marketplace. But we need to disable the config for one or the other so that it won't respond to user actions like comments/commands.

we could have two configs .ubiquibot-config.yml and .ubiquibot-config.dev.yml and env variable that switches the bot between production and development

Lets do that.

0x4007 commented 1 day ago

@whilefoo perhaps you can take this one on?

whilefoo commented 1 day ago

we could have two configs .ubiquibot-config.yml and .ubiquibot-config.dev.yml and env variable that switches the bot between production and development

whilefoo commented 15 hours ago

/start

ubiquity-os[bot] commented 15 hours ago
Deadline Mon, Oct 7, 11:34 AM UTC
Beneficiary 0xA0B11F474d8ECE1205d38c66d5F2bE8917675d60

[!TIP]

  • Use /wallet 0x0000...0000 if you want to update your registered payment wallet address.
  • Be sure to open a draft pull request as soon as possible to communicate updates on your progress.
  • Be sure to provide timely updates to us when requested, or you will be automatically unassigned from the task.
ubiquity-os-beta[bot] commented 15 hours ago
Deadline Mon, Oct 7, 11:34 AM UTC
Beneficiary 0xA0B11F474d8ECE1205d38c66d5F2bE8917675d60

[!TIP]

  • Use /wallet 0x0000...0000 if you want to update your registered payment wallet address.
  • Be sure to open a draft pull request as soon as possible to communicate updates on your progress.
  • Be sure to provide timely updates to us when requested, or you will be automatically unassigned from the task.