• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

greptileai / supabase-mirror / 22885891335
73%

Build:
DEFAULT BRANCH: master
Ran 10 Mar 2026 03:37AM UTC
Jobs 1
Files 78
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

10 Mar 2026 02:34AM UTC coverage: 73.263%. Remained the same
22885891335

push

github

web-flow
Organize pg meta queries for studio (#43562)

## Context

We reached to a consensus that we'll keep manually written queries
within the `pg-meta` package

I'll shift queries over in several PRs but wanted to double check if the
changes here is a good folder structure

## Changes involved

- Am organizing dashboard queries in `pg-meta` based on product
  - So folder structure will be `/sql/studio/[product]/*.ts`
- Every constant will be exported directly from `pg-meta`'s index
- So consumption in dashboard will just be `import { xxx } from
'@supabase/pg-meta`

cc @avallete and @soedirgo on this one - lemme know if this is alright,
or if there's a preferred way to do this

834 of 943 branches covered (88.44%)

Branch coverage included in aggregate %.

3079 of 4398 relevant lines covered (70.01%)

110.99 hits per line

Jobs
ID Job ID Ran Files Coverage
1 studio-tests - 22885891335.1 10 Mar 2026 03:37AM UTC 78
73.26
GitHub Action Run
Source Files on build 22885891335
  • Tree
  • List 78
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #22885891335
  • fc7fb50a on github
  • Prev Build on master (#22879998024)
  • Next Build on master (#22894164239)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc