Agent Worktrees / Branching / Schema Mismatches
❔Advice
I'm coming from the postgres / prisma / neon db world, and have found a difficult time adjusting to a workflow that allows schema changes across multiple git branches.
Given that my convex account only has one development enviornment, if i create multiple branches that each have a schema modification, i quickly face an issue with schema mismatch errors (i understand why, but am looking for advise how to avoid it)
Does anyone have advice around how to create a development setup to support this? Should i be utilizing preview branches? I feel like this is becoming increasingly more relevant as i utilize agents to work on things in isolated worktrees - the schema mismatch errors cause them to get caught up and the errors create a insurmountable amount of backpressure, preventing the agent from completing and validating its work
Any advice would be appreciated!
Given that my convex account only has one development enviornment, if i create multiple branches that each have a schema modification, i quickly face an issue with schema mismatch errors (i understand why, but am looking for advise how to avoid it)
Does anyone have advice around how to create a development setup to support this? Should i be utilizing preview branches? I feel like this is becoming increasingly more relevant as i utilize agents to work on things in isolated worktrees - the schema mismatch errors cause them to get caught up and the errors create a insurmountable amount of backpressure, preventing the agent from completing and validating its work
Any advice would be appreciated!
