search

ubiquity-os-marketplace / command-start-stop

Manager user commands to assign / un-assign themselves to tasks.
0 stars 18 forks source link

chore: update assign message #48

Closed 0x4007 closed 2 months ago

0x4007 commented 2 months ago

Resolves #47

0x4007 commented 2 months ago

Got it working on #49

This BOT_USER_ID thing is breaking the deploy.

@0x4007 org secrets:

image
0x4007 commented 2 months ago

I'm really confused! I just added BOT_USER_ID to UbiquiBot org secrets and NOW the wrangler secrets upload works. I thought its supposed to be set from our forks?

https://github.com/ubiquibot/command-start-stop/actions/runs/10862228060/job/30146968045#step:6:65

Check the previous 4 (failed) attempts. The only difference is that BOT_USER_ID was not set in Ubiquibot org secrets until the 5th attempt. I didn't change my own org secrets on my fork between the 4th and 5th run.

Adding to the confusion, but due to limitations with the kernel and the other plugins, they cant communicate directly with eachother unless they are on separate Cloudflare accounts. So I have access to both Ubiquity Workers and my personal account with the kernel. So there's a lot going on and I didn't want to create a brand new account just for this one off test.
0x4007 commented 2 months ago

I'm assuming its secrets related. That's the only difference. This error is terribly vague.

@ubiquibot/command-start-stop@development

image

@0x4007/command-start-stop@chore-new-assign-design

image

Looks like we're back to the same problem with that secret. We should probably revert.

0x4007 commented 2 months ago

Just realized I accidently pushed this directly to ubiquibot organization so the branch was running from the ubiquibot owned repository, which clears up all of my confusion.