ubiquity / ubiquibot-telegram

Your AI powered repository manager (on Telegram.)
1 stars 8 forks source link

Link Telegram Database #15

Closed seprintour closed 1 year ago

seprintour commented 1 year ago

Resolves #3

seprintour commented 1 year ago

@pavlovcik check this

seprintour commented 1 year ago

Channel support added @web4er, Reinstall bot with post and edit message permission

web4er commented 1 year ago

Code looks good, but bot is not working after some recent changes.

image

seprintour commented 1 year ago

Code looks good, but bot is not working after some recent changes.

make sure variables are changed to the new names on cloudflare as well and filled accordingly

web4er commented 1 year ago

make sure variables are changed to the new names on cloudflare as well and filled accordingly

I deleted the old deployment and deployed the fresh changes. Here are the variables on Cloudflare.

image

seprintour commented 1 year ago

I deleted the old deployment and deployed the fresh changes. Here are the variables on Cloudflare.

github_installation_token

seprintour commented 1 year ago

GITHUB_INSTALLATION_TOKEN not INSTALLATION_TOKEN anymore

web4er commented 1 year ago

GITHUB_INSTALLATION_TOKEN not INSTALLATION_TOKEN anymore

Do I have to add it manually? because I did yarn setup-key already.

seprintour commented 1 year ago

GITHUB_INSTALLATION_TOKEN not INSTALLATION_TOKEN anymore

Do I have to add it manually? because I did yarn setup-key already.

I think your code is not updated, because the variable names have changed so that should change automatically too.

You can try deleting everything, updating your branch and running setup-key again

seprintour commented 1 year ago

We have to be done with this soon, its been open for too long..

We have #17

web4er commented 1 year ago

I think your code is not updated, because the variable names have changed so that should change automatically too.

Yes, I thought it was missing that in code. Working now.

seprintour commented 1 year ago
  • yarn setup-key
  • yarn deploy

These are handled automatically by the Github actions, Just some variable names change in secret

seprintour commented 1 year ago

It looks like my earlier requested changes were not implemented please confirm the status and then I can approve and merge.

Perhaps they were on the other pull request that this one is based off of?

These changes were made in #17

seprintour commented 1 year ago

You made the review and it got implemented here: https://github.com/ubiquity/telegram-ubiquibot/pull/17/commits/c476f883910c75d8cdd77ae6fe28b374b5ad81de

seprintour commented 1 year ago

@pavlovcik can you add SUPABASE_URL and SUPABASE_KEY to .env and rename INSTALLATION_TOKEN to GITHUB_INSTALLATION_TOKEN

seprintour commented 1 year ago

and TOKEN to TELEGRAM_BOT_TOKEN in secrets

0x4007 commented 1 year ago

@pavlovcik can you add SUPABASE_URL and SUPABASE_KEY to .env and rename INSTALLATION_TOKEN to GITHUB_INSTALLATION_TOKEN

You should have access to manipulate the secrets in this repository. I assume you can handle everything except for the Telegram bot token (but I just checked, and this is already in our secrets as of two weeks ago.)

seprintour commented 1 year ago

You should have access to manipulate the secrets in this repository

I only have access to cloudflare variables

0x4007 commented 1 year ago

I updated your permissions to maintain role. Can you see this? https://github.com/ubiquity/telegram-ubiquibot/settings/secrets/actions

seprintour commented 1 year ago

Can you see this?

No, its a 404 page

0x4007 commented 1 year ago

I sent you dm on telegram