See preview branch state
Inventory the branch metadata needed to understand whether a preview exists, is healthy, and still has active work.
Integration / Supabase
Keep preview branches aligned with the work that created them.
Supabase preview branches are isolated environments for pull-request work. LintCycle checks their lifecycle alongside GitHub and the rest of your preview stack.
The operating principle
A branch is only one part of the preview.
LintCycle treats Supabase state as provider evidence, then combines it with pull-request and infrastructure signals before recommending review.
Why Supabase
The context stays attached to the recommendation.
Correlate across providers
Keep the database branch in the same evidence trail as the GitHub pull request and Railway environment.
Avoid destructive access
LintCycle does not delete branches, change database configuration, or expose project credentials.
How it works
A short path from connection to review.
Choose Supabase inventory
Connect the projects that create preview branches for repositories in the current LintCycle workspace.
Align branch and PR state
LintCycle compares branch metadata with the originating repository and pull-request lifecycle.
See missing or retained branches
Review findings when a preview branch is absent, unhealthy, or appears to outlive its work.
Questions
The boundaries, in plain language.
Can LintCycle query customer database contents?
No. The integration is for preview-resource inventory, not application data access.
Can LintCycle delete a preview branch?
No. All provider actions remain read-only in version one.
What happens when branch correlation is ambiguous?
LintCycle withholds the finding instead of presenting uncertainty as a confident cleanup recommendation.
Close the loop
Put Supabase preview branches in the same lifecycle view.
Start with ten repositories and every provider needed to explain their preview state.