-
-
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
Feature Request: Transaction configuration on a per migration basis
feature
good first issue
help wanted
#659
opened Dec 11, 2019 by
gibsonjoshua55
1 of 3 tasks
No order is guaranteed if migrations have the same date
bug
feature
good first issue
help wanted
#646
opened Aug 28, 2019 by
abolognino
1 of 3 tasks
db-migrate fails to show version if database.json missing
bug
good first issue
help wanted
Nice to have
#568
opened May 8, 2018 by
vladimirtiukhtin
1 task
Allow column comments
feature
good first issue
help wanted
Nice to have
Not Planned
#558
opened Mar 21, 2018 by
Nosfistis
1 of 3 tasks
Add executeAfter setting to scope configuration
feature
good first issue
help wanted
#511
opened Nov 1, 2017 by
wzrdtales
Add group setting to scope config
feature
good first issue
help wanted
#510
opened Nov 1, 2017 by
wzrdtales
Add excludeFromAll setting to scope config
feature
good first issue
help wanted
#509
opened Nov 1, 2017 by
wzrdtales
EventEmitter memory leaks
good first issue
help wanted
Refactoring
#421
opened Oct 4, 2016 by
foysavas
Is there a way to hook into an "afterMigrate" event?
documentation
feature
good first issue
help wanted
#384
opened Jul 11, 2016 by
mpalmerlee
Add a docker configuration to ease testing
feature
good first issue
help wanted
#372
opened May 11, 2016 by
Maxwell2022
Support "databaseless" execution commands
feature
good first issue
help wanted
#338
opened Jan 17, 2016 by
wzrdtales
ProTip!
Add no:assignee to see everything that’s not assigned.