gwen.works
student life social platform
1Closes #[issue number]
2
3<!--
4Once the PR is ready for review, add the `review:ready` label.
5-->
6
7Checks before adding `review:ready`:
8
9- [ ] 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)
10- [ ] I've added changesets if necessary (see the comment by the changeset bot below)
11- [ ] If some commits were made without commit lints (`--no-verify` flag), I ran `yarn lintfix` and `yarn format` afterwards
12- [ ] I've tested the changes locally
13- [ ] If I added / removed environment variables:
14 - [ ] I've updated the `.env.example` file
15 - [ ] I've updated the `packages/api/src/env.ts` file
16 - [ ] 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)
17- [ ] If relevant, I added database seeding data to by modifying `packages/db/seed/index.ts`
18- [ ] 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): see `fulltextsearch.sql`, copy-paste the `CREATE OR REPLACE FUNCTION update_TABLE_search()` statement, removing the deleted fields from its implementation, for every `TABLE` that uses your now-deleted field in its search tsvector update trigger function
19- [ ] If relevant, I've updated the technical documentation:
20 - [ ] [The wiki](https://git.inpt.fr/churros/wiki)
21 - [ ] The various CONTRIBUTING.md files