Skip to content
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

Docs: add info about troubleshooting dirty database #361

Merged

Conversation

mknycha
Copy link
Contributor

@mknycha mknycha commented Mar 24, 2020

[#337]

```
Once you force the version and your migration was fixed, your database is 'clean' again and you can proceed with your migrations.

For details and example of usage see [this comment](https://github.com/golang-migrate/migrate/issues/282#issuecomment-530743258).
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was not sure if adding a link to a comment in an issue is ok, I have just felt like it's already well described there and I wanted to give credit where it's due.
If you want me to rewrite it, that's also fine.

@coveralls
Copy link

coveralls commented Mar 24, 2020

Pull Request Test Coverage Report for Build 729

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 53.08%

Totals Coverage Status
Change from base Build 728: 0.0%
Covered Lines: 2559
Relevant Lines: 4821

💛 - Coveralls

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants