Open romain-sen opened 1 year ago
So for type generation it seems like there is an easy way in the CLI action. I don't know if migrations in Supabase CLI action make sense to me. Not sure how I would manage them there.
Would it be relevant to create an action that, when a file is changed in supabase/migrations/*.sql, updates the types + pushes the migrations to the project db? What do you think?
I think so. It's the other way around though. It should update the database with the new migrations and then generate the types from the new database structure.
This is a great idea. For sure.
How can we add the Supabase CLI action to the workflow properly ? Do we also need to change how we write migrations ?