-
-
Notifications
You must be signed in to change notification settings - Fork 360
Issues: db-migrate/node-db-migrate
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Create a toolset to check the current configuration for issues
feature
#312
opened Sep 21, 2015 by
wzrdtales
Add excludeFromAll setting to scope config
feature
good first issue
help wanted
#509
opened Nov 1, 2017 by
wzrdtales
error when initialization of migration failes before any action.
bug
#689
opened Apr 22, 2020 by
wzrdtales
Working with newly created db for migrations in postgres
#723
opened Mar 1, 2021 by
noamski
3 tasks done
Is there any way to override DATABASE_URL so I can determine which db to run migration for?
#738
opened Jun 3, 2021 by
cc3613
2 tasks
.db-migraterc at the root of the project is being ignored
#759
opened Oct 20, 2021 by
flisboac
1 of 3 tasks
Config: Allow default value for when environment variables not set
#765
opened Jan 20, 2022 by
kael-shipman
1 of 3 tasks
Configuration defaultEnv default value is not readed
#769
opened Feb 22, 2022 by
exejutable
1 task done
Argv bug when running createDatabase using the Programmable API as part of a Jest test run
#796
opened Aug 8, 2022 by
mmajkafmp
1 of 3 tasks
Question: possible to use an abstract source of migrations that is not a file system directory
#797
opened Oct 12, 2022 by
mike-hogan
drop index 'ifExists' and createIndex 'ifNotExists' options
#833
opened Jul 26, 2024 by
kevinand11
1 of 3 tasks
Previous Next
ProTip!
Adding no:label will show everything without a label.