ianmitchell/prisma-migration-warning
Checks Pull Requests for potentially unsafe Prisma Migrations
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stalelast commit Feb 12, 2022
- License
- MIT
- Runtime
- Deprecated runtime
Pinned Snippet
uses: ianmitchell/prisma-migration-warning-action@b200ee07ef2debd96a3695937f9feb3beb94818e # v1tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| main-branch | Name of the main branch | no | main |
| path | Path to your prisma directory | no | prisma |
| warning | Post a comment in the PR warning about the potentially unsafe migration | no | true |
| message | The warning message to post when potentially unsafe migrations are detected | no | | :warning: Migration Warning | |:---------------------------| | It looks like this pull request modifies your Prisma schema in addition to other files. To minimize errors or downtime during deployment, make sure your schema changes don't rename or remove fields that are actively being used in production. You may want to separate your changes into two Pull Requests; one to change your application logic and another followup that updates your schema. | |
| repeat | Whether to repeat warnings or not | no | false |
| fail | Whether to fail or not when potentially unsafe migrations are detected | no | false |
Outputs
no outputs