Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: support fetching migration history table to files #2113

Merged
merged 1 commit into from
Apr 29, 2024

Conversation

sweatybridge
Copy link
Contributor

@sweatybridge sweatybridge commented Apr 3, 2024

What kind of change does this PR introduce?

feature

What is the new behavior?

supabase migration fetch to download statements in migration history table as local migration files.

Additional context

Add any other context or screenshots.

@coveralls
Copy link

coveralls commented Apr 3, 2024

Pull Request Test Coverage Report for Build 8876275466

Details

  • 7 of 47 (14.89%) changed or added relevant lines in 3 files are covered.
  • 5 unchanged lines in 1 file lost coverage.
  • Overall coverage decreased (-0.2%) to 57.993%

Changes Missing Coverage Covered Lines Changed/Added Lines %
cmd/migration.go 7 10 70.0%
internal/migration/history/history.go 0 6 0.0%
internal/migration/fetch/fetch.go 0 31 0.0%
Files with Coverage Reduction New Missed Lines %
internal/gen/keys/keys.go 5 11.76%
Totals Coverage Status
Change from base Build 8874184176: -0.2%
Covered Lines: 6501
Relevant Lines: 11210

💛 - Coveralls

@sweatybridge sweatybridge changed the title feat: support fetching migration history to local feat: support fetching migration history table to files Apr 29, 2024
@sweatybridge sweatybridge merged commit cecb69b into develop Apr 29, 2024
9 checks passed
@sweatybridge sweatybridge deleted the fetch-history branch April 29, 2024 09:28
@github-actions github-actions bot mentioned this pull request Apr 30, 2024
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.

2 participants