Dev Feed

@tgriesser we've actually implemented something like this at kwiff Our motivation was for local integration tests where we found our spin-up phase running full migrations, and it just ate time out of our test suite. cc @tomasniculae

@sunsheeppoplar you around to fix the conflict?

PullRequestReviewEvent

I agree. Feels like an obvious roll-in to `master` on the next release as the new link also works for me.

A step towards helping with these: https://github.com/knex/knex/issues/4678 https://github.com/knex/knex/issues/5818 https://github.com/knex/knex/issues/1596

PullRequestReviewEvent

```suggestion This is because MySQL uses an `Implicit Commit` for many schema related commands. ```

We could advise here: `For this reason, as best practice, every DDL change should be isolated to it's own file for clean "complete status" and rollback strategy.`

If there are any users of this package who would like to help with maintaining it I would be grateful to hear from you. I do my best, but time is limited. In particular anyone interested in building out tests for CI/CD would be very useful.

Hi @ataylorme, Actually I noticed this again recently and what I found was that one of the "double comments" I observed was from built-in Github Action behaviour picked up from `stdout` i.e. not from this package. I confirmed this by removing `eslint-annotate-action` from our pipelines entirely and we still got ESLint comments annotated to our PRs, so we've dropped using this dependency. I'm not sure if you're aware of that built-in support specifically(?), but the built-in felt "good enough" not to fiddle around with further config. Did I miss some documentation on this?

PullRequestReviewEvent