docs: document scoped db:seed:demo as the prod-safe seed exception - #29
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ce que fait cette PR
Documente le script
db:seed:demo(livré en #28) dans CLAUDE.md et README, et clarifie qu'il est l'exception autorisée au « jamais de seed contre la prod ».db:seed:demo(additif, scopéwhere: { userId }) peut tourner contre la prod ; ledb seeddestructif (user.deleteMany()global) reste interdit en prod. Section Seed de démo + bloc des scripts npm mis à jour.Pourquoi
Le commit de doc a été poussé après le merge de #28, il n'était donc pas inclus. Cette PR le rattache à
mainproprement, pour que la convention reflète la réalité (seed prod scopé autorisé).Comment tester
Relecture de CLAUDE.md et README — aucun changement de code.
Checklist