Greg Weber

Merging this does not preclude having `--to` and `--dry-run`. I can change the flag to `-f` `--filter`. Keeping it as a the top-level argument rather than sub-command I think helps...

@dossy fundamentally this tool is not designed the way you want it to be designed. You can use it the way you want, and I can use it the way...

transactional migrations solve the problem to the extent that when there is a migration failure things won't be left in an invalid state. So it's simple at that point to...

I appreciate what you are doing to move this project forward: you are a being a great maintainer in all other aspects. There's just some things we can improve on...

> However, it is possible for two or more branches to diverge, and depending on the order in which those branches are merged and the version numbers of the migrations...

@dossy do you use git flow or trunk-based development?

@dossy pretty much everyone uses branch-based development, at least that uses Github and has more than one contributor. With trunk-based there is only one special long-lived trunk branch (main). Releases...

@Retch I merged the latest into my branch. I use the migration filtering feature all the time, give it a try and report back.

This PR is updated to allow for multiple migrations to be specified rather than just one.

#256 for automatically applying multiple migrations at once by specifying one does not satisfy my workflows: I would still have to engage in workarounds. However, someone that wants that functionality...