Fix #16

[drakmail]

Create db-migrate schema before creation of migrations table to fix #16

[commitlint-wzrdtales]

There were the following issues with this Pull Request

• Commit: 016a8ff
  • ✖ message may not be empty
    , - ✖ type may not be empty

You may need to change the commit messages to comply with the repository contributing guidelines.

---

🤖 This comment was generated by commitlint[bot]. Please report issues here.

Happy coding!

[drakmail]

PS. Seems that travis-ci build is broken

[drakmail]

I'm fixed travis-ci issue in #50

[wzrdtales]

thank you for your contribution!

have to check on the dependencies if this has any side effects.

[commitlint-wzrdtales]

There were the following issues with this Pull Request

• Commit: b5daad4
  • ✖ message may not be empty
    , - ✖ type may not be empty

You may need to change the commit messages to comply with the repository contributing guidelines.

---

🤖 This comment was generated by commitlint[bot]. Please report issues here.

Happy coding!

[commitlint-wzrdtales]

There were the following issues with this Pull Request

• Commit: fcf9f26
  • ✖ message may not be empty
    , - ✖ type may not be empty
• Commit: 397bf4d
  • ✖ message may not be empty
    , - ✖ type may not be empty

You may need to change the commit messages to comply with the repository contributing guidelines.

---

🤖 This comment was generated by commitlint[bot]. Please report issues here.

Happy coding!

[drakmail]

I'm rebased over the master branch, so tests now is passed (and also fixed a bug)

[wzrdtales]

a little late, however, this would effectively change the schema, which is not an intended behavior. if you by any chance look again at this. do you know what was your intention?