Closed seprintour closed 1 year ago
@pavlovcik check this
Channel support added @web4er, Reinstall bot with post and edit message permission
Code looks good, but bot is not working after some recent changes.
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
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.
I deleted the old deployment and deployed the fresh changes. Here are the variables on Cloudflare.
github_installation_token
GITHUB_INSTALLATION_TOKEN
not INSTALLATION_TOKEN
anymore
GITHUB_INSTALLATION_TOKEN
notINSTALLATION_TOKEN
anymore
Do I have to add it manually? because I did yarn setup-key
already.
GITHUB_INSTALLATION_TOKEN
notINSTALLATION_TOKEN
anymoreDo 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
We have to be done with this soon, its been open for too long..
We have #17
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.
- yarn setup-key
- yarn deploy
These are handled automatically by the Github actions, Just some variable names change in secret
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
You made the review and it got implemented here: https://github.com/ubiquity/telegram-ubiquibot/pull/17/commits/c476f883910c75d8cdd77ae6fe28b374b5ad81de
@pavlovcik can you add SUPABASE_URL
and SUPABASE_KEY
to .env and rename INSTALLATION_TOKEN
to GITHUB_INSTALLATION_TOKEN
and TOKEN
to TELEGRAM_BOT_TOKEN
in secrets
@pavlovcik can you add
SUPABASE_URL
andSUPABASE_KEY
to .env and renameINSTALLATION_TOKEN
toGITHUB_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.)
You should have access to manipulate the secrets in this repository
I only have access to cloudflare variables
I updated your permissions to maintain
role. Can you see this?
https://github.com/ubiquity/telegram-ubiquibot/settings/secrets/actions
Can you see this?
No, its a 404 page
I sent you dm on telegram
Resolves #3