Closes #[issue number]
Checks before adding review:ready
:
- My branch is up-to-date with upstream's main branch, at the latest tag or more recent (this prevents, amongst other things, creating prisma migrations dated in the past relative to the current deployed migrations)
- I've added changesets if necessary (see the comment by the changeset bot below)
- If some commits were made without commit lints (
--no-verify
flag), I ranyarn lintfix
andyarn format
afterwards - I've tested the changes locally
- If I added / removed environment variables:
- I've updated the
.env.example
file - I've updated the
packages/api/src/env.ts
file - I opened a MR to inp-net/k8s to update the production environment variables (can be done by a core team member if the new variable is a secret)
- I've updated the
- If relevant, I added database seeding data to by modifying
packages/db/seed/index.ts
- If I removed fields from a database table (prisma model) I also updated trigger functions that computes fulltext search vectors (fields with the
Unsupported("tsvector")
type in the prisma schema): seefulltextsearch.sql
, copy-paste theCREATE OR REPLACE FUNCTION update_TABLE_search()
statement, removing the deleted fields from its implementation, for everyTABLE
that uses your now-deleted field in its search tsvector update trigger function - If relevant, I've updated the technical documentation:
- The wiki
- The various CONTRIBUTING.md files