Skip to content

Conversation

@sweatybridge
Copy link
Contributor

What kind of change does this PR introduce?

Bug fix, feature, docs update, ...

What is the current behavior?

Please link any relevant issues here.

What is the new behavior?

Feel free to include screenshots if it includes visual changes.

Additional context

Add any other context or screenshots.

@sweatybridge sweatybridge requested a review from a team as a code owner February 9, 2026 10:05
@coveralls
Copy link

Pull Request Test Coverage Report for Build 21820986475

Details

  • 20 of 24 (83.33%) changed or added relevant lines in 3 files are covered.
  • 6 unchanged lines in 2 files lost coverage.
  • Overall coverage increased (+0.8%) to 59.158%

Changes Missing Coverage Covered Lines Changed/Added Lines %
internal/postgresConfig/get/get.go 7 8 87.5%
internal/postgresConfig/update/update.go 6 7 85.71%
internal/postgresConfig/delete/delete.go 7 9 77.78%
Files with Coverage Reduction New Missed Lines %
internal/postgresConfig/update/update.go 1 92.31%
internal/gen/keys/keys.go 5 12.9%
Totals Coverage Status
Change from base Build 21819468549: 0.8%
Covered Lines: 7613
Relevant Lines: 12869

💛 - Coveralls

@sweatybridge sweatybridge merged commit cee2c5b into develop Feb 9, 2026
10 of 11 checks passed
@sweatybridge sweatybridge deleted the pg-test branch February 9, 2026 10:23
@supabase-cli-releaser supabase-cli-releaser bot mentioned this pull request Feb 10, 2026
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