Skip to content

Conversation

ahtcx
Copy link
Contributor

@ahtcx ahtcx commented Oct 10, 2025

What kind of change does this PR introduce?

I use an ORM that generates a meta directory in the migrations directory. This change should ignore any directories when listing local migrations.

What is the current behavior?

Currently the CLI outputs the following when a meta directory exists in the migrations directory:

Skipping migration meta... (file name must match pattern "<timestamp>_name.sql")

What is the new behavior?

Directories in the migrations directory will be skipped silently.

Additional context

I want to use the Supabase migrations instead of the built-in ORM migration tool as it integrates more smoothly into my workflow.

I'm not a Go dev and I don't have a dev environment set up but I figured this is a tiny change so it hopefully isn't an issue. I was initially going to create an issue but decided I might as well make it a PR, apologies if I missed anything! I can create an issue if this needs more work.

Thanks!

@ahtcx ahtcx requested a review from a team as a code owner October 10, 2025 00:09
@coveralls
Copy link

Pull Request Test Coverage Report for Build 18392443203

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • 5 unchanged lines in 1 file lost coverage.
  • Overall coverage decreased (-0.03%) to 54.67%

Files with Coverage Reduction New Missed Lines %
internal/gen/keys/keys.go 5 12.9%
Totals Coverage Status
Change from base Build 18366617803: -0.03%
Covered Lines: 6409
Relevant Lines: 11723

💛 - Coveralls

@sweatybridge
Copy link
Contributor

Thanks for contributing. Looks like a good QoL fix.

@sweatybridge sweatybridge merged commit db2b259 into supabase:develop Oct 12, 2025
13 of 20 checks passed
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