Closed alex-voodoo closed 9 months ago
TIL that it is better to send the DB migration in a separate PR.
The reason is: the DB schemas in main
and stable
have diverged, and the migration that targets main
may not work for stable
(the migrations refer to their parents). I had to fix this on stable
because the deployment failed.
The safer way is: first land the change to the models into main
, then cherry-pick it into the stable
, then generate migrations in both branches and commit independently.
This patch addresses a discussion about better wording in the self-assessment form.