This is really great. Managing migrations without locking the table can be a real huge pain-point. And having a dedicated project likely covers more edge cases than an internal tool would (as is evident looking at the issues list).

With that said, it looks like it could be used not just as a stand alone tool but also embedded within a Go application since it does export its API. In my case I'd love to use it from my existing tooling. I couldn't find any documentation on how to do that, though.

I'll probably dig more into that later.