Alex Evanczuk

Possibly a separate issue, but I was thinking it would be cool to send a pull request with this, along with some other work that allows contracts to play nicer...

Hey thanks for your response @egonSchiele . I've lost some of the context, but I'll do my best to summarize the approaches. Firstly it does sound like a bug that...

Hi @kyrofa @ilyakatz and @tleish ! We're also looking to allow for many values of `DataMigrate.config.data_migrations_path`. Ideally, this could accept a `glob`, but it would be fine if it just...

Thanks @ilyakatz ... ya know, as it turns out, we're already able to pass multiple paths to the configuration! The value ends up being massed through to the `MigrationContext` which...

Can do! We had some odd failures in CI related to this change so I'm just going to dig in and confirm it's related to our setup! Then I'll add...

@jez > Is that what you're saying? Not exactly. There are two separate concerns: (1) avoiding `NameError` and (2) making sure zeitwerk works. For (1), neither the current behavior or...

@gustavodiel So we were able to get migrations to run locally with this: ``` DataMigrate.configure do |config| default_path = DataMigrate::Config.new.data_migrations_path package_packs = Stimpack::Packs.all.map { |pack| pack.path.relative_path_from(Dir.pwd).join('db/data/') }.map(&:to_s) config.data_migrations_path = [default_path,...

@afhoffman I saw this pop up referencing the other PR. Also wanted to plug just using the vanilla `gh` CLI client in your CD for releases. I switched over to...

Hello - I was wondering if there is a PR out for this that could be merged. If not, what sort of work can be done? I tried using the...

Thanks @pboling . Will take a look when I get a chance!