feat: Prisma migration setup - Supabase branch initialization#257
feat: Prisma migration setup - Supabase branch initialization#257JSONbored wants to merge 42 commits intofeat/mcp-and-othersfrom
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
…pendency This migration creates the content_unified view that mv_content_stats depends on. The view unifies content from the content table, allowing the parent migration 20251030044243_recreate_mv_content_stats.sql to succeed on fresh branches. This change will trigger GitHub Integration to create the Supabase branch properly.
… additional test cases
… additional test cases
…n for CommonJS compatibility #2
…ation with Inngest functions
…on with server actions, and update API route configurations
…or integration testing and enhance type safety in Prismocker
…nd security checks with Trunk integration
…d code quality and performance standards
…nce README with new features, and add lifecycle method tests
…m Lefthook and Jest, streamline project structure for better maintainability
This PR sets up the Supabase branch structure for the Prisma migration work.
Changes
supabase/directory at repository root20251214190000_initial_schema.sql)Purpose
This PR triggers Supabase GitHub Integration to create the
feat_prisma-migrationbranch and apply migrations.Next Steps