actions-marketplace-validations/migrator-conflicts
Check if migrations in your branch aren't conflicting with the base branch when you raise a pull request.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stalelast commit Jul 3, 2022
- License
- MIT
- Runtime
- Deprecated runtime
Pinned Snippet
uses: actions-marketplace-validations/prashantraj18198_migrator-conflicts@0c6559ce6eb5ff902fe4508c9c89dd32aadbfedc # no releases — HEAD as of 2026-07-10tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| github_token | Github token, required to comment on pull requests | yes | — |
| base_branch | Base branch to compare current migrations against | no | — |
| current_branch | Current branch to compare against the base branch | no | — |
| mention_author | Tag the author in comment if 'mention_author' is marked 'true' | no | false |
| migration_delimiter | Delimiter to use for the files to get the migration version. If your migrations files are named with '_' delimiter, for example 'migrations/20220702213559_initial_migration.sql' here the delimiter is '_'. Delimiter is used to fetch the migration version for a file. In the above example the migration version is 20220702213559. | no | _ |
| migration_directories | List of migration directories to compare for conflicts. Each directory in 'current_branch' is compared against the 'base_branch' for migration conflicts. For example, if migration_directories = ['users/migrations', 'orders/migrations'], 'users/migrations' of current_branch is compared against 'users/migrations' of base_branch. | yes | — |
Outputs
no outputs