openmindua/Alembic Actions
Collection of GitHub Actions for managing Alembic database migrations in CI/CD workflows
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| action | Which action to run: 'review', 'test', or 'deploy' | yes | — |
| dialect | SQL dialect to use for Alembic (postgresql, mysql, etc.) | no | postgresql |
| alembic_ini | Path to alembic.ini file | no | alembic.ini |
| migration_path | Path to Alembic migrations directory | no | migrations |
| database | Database name for multi-database setup (optional) | no | — |
| revision_range | Optional revision range for SQL generation (e.g., 'head:base') | no | head |
| pr_revisions_only | Only generate SQL for migrations in the current PR (true/false) | no | true |
| database_url | Database URL for testing/deploying migrations | no | — |
| test_data_script | Optional script to load test data (test action only) | no | — |
| backup | Whether to create a database backup before applying migrations (deploy action only) | no | true |
| target_revision | Target revision to migrate to (deploy action only, default: head) | no | head |
Outputs
no outputs