Automated Supabase Migrations

seprintour commented 1 year ago

Problem:

Currently, managing database migrations in Supabase requires manual execution of migration scripts. This process can be error-prone, time-consuming, and lacks the efficiency needed for modern development workflows. As our project grows, the need for automation becomes increasingly evident to ensure seamless database updates.

Proposed Solution:

I propose automating Supabase migrations by leveraging GitHub Deployment workflows. This enhancement will significantly improve our development process, making database schema updates a hassle-free and reliable part of our continuous integration pipeline.

Here is a working example of automated migration on supabase: https://github.com/ubiquity/ubiquibot/blob/development/.github/workflows/build.yml

We can copy that over, modify the secrets name and make some minor adjustments

File path to be migrated: https://github.com/ubiquity/ubiquibot-telegram/tree/development/supabase/migrations

Supabase Project ID Secret: SUPABASE_PROJECT_ID Supabase Access Token: SUPABASE_PROJECT_KEY Supabase DB Password: SUPABASE_DB_PASSWORD

seprintour commented 1 year ago

/start

ubiquibot[bot] commented 1 year ago





Deadline
Sun, 24 Sep 2023 06:56:42 UTC


Registered Wallet
0x3623338046b101ecEc741De9C3594CC2176f39E5

Tips:

Use /wallet 0x0000...0000 if you want to update your registered payment wallet address @user.
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 bounty.

ubiquibot[bot] commented 1 year ago

Reviewer Rewards

pavlovcik: [ CLAIM 0.2 WXDAI ]

ubiquibot[bot] commented 1 year ago

Task Assignee and Creator Reward

[ CLAIM 95.1 WXDAI ]

0x362333804...2176f39E5

If you've enjoyed your experience in the DevPool, we'd appreciate your support. Follow Ubiquity on GitHub and star this repo. Your endorsement means the world to us and helps us grow!

We are excited to announce that the DevPool and UbiquiBot are now available to partners! Our ideal collaborators are globally distributed crypto-native organizations, who actively work on open source on GitHub, and excel in research & development. If you can introduce us to the repository maintainers in these types of companies, we have a special bonus in store for you!

seprintour commented 1 year ago

Now, somethings up here.. It's not down or bad, it's just irregular.

Hmm

0x4007 commented 1 year ago

Well it combined your rewards for identifying the issue and fixing it. It just gave you a lot of rewards for issue creation, which we will eventually limit to the bounty price. I think it looks fine.

I also got paid $0.2 for saying "look fine" lol

seprintour commented 1 year ago

Well it combined your rewards for identifying the issue and fixing it. It just gave you a lot of rewards for issue creation, which we will eventually limit to the bounty price. I think it looks fine.

It added it in the permit comment but when i try to claim, it does not add the creator amount

I traced it down to this line: https://github.com/ubiquity/ubiquibot/blob/f41c03691d5849e546db8bfb62b907122294a820/src/handlers/payout/action.ts#L415

It's supposed to be priceInEth not assigneeReward.reward[0].priceInEth

0x4007 commented 1 year ago

You can turn your comment into a new issue and get around to it when you are not actively working on 2-3 tasks or whatever. You get paid for identifying the issue.

0x4007 commented 1 year ago

@seprintour its in your best interest to file the issue asap so that you can take credit for filing it. Even if you end up not working on it the incentives should make it more profitable for you to identify and file issues asap. Otherwise somebody else can make the issue and you don't get credit.

ubiquity / ubiquibot-telegram