Choose the repositories
Monitor only the repositories that belong in the workspace rather than granting broad, unexplained access.
Integration / GitHub
Pull-request context for every finding.
GitHub supplies the lifecycle signal: which repository owns the work, whether the pull request is open or closed, and when that state changed. LintCycle uses that context without writing to your repositories.
The operating principle
The pull request is context, not authority.
A merged pull request is one signal. LintCycle compares it with provider inventory and deterministic rules before it produces a finding.
Why GitHub
The context stays attached to the recommendation.
Read lifecycle state
Use repository and pull-request metadata to understand whether preview work is still active, merged, or closed.
Keep the source visible
Every correlated finding points back to the pull request evidence that contributed to the decision.
How it works
A short path from connection to review.
Connect the GitHub App
Authorize the read-only installation and select the repositories the LintCycle workspace should inventory.
Read pull-request state
LintCycle records the minimum repository and pull-request metadata needed for deterministic correlation.
Match work to resources
Pull-request evidence is compared with Railway and Supabase inventory before a finding is created.
Questions
The boundaries, in plain language.
Can LintCycle merge, close, or edit pull requests?
No. The version-one provider boundary is read-only and includes no pull-request write actions.
Does a closed pull request always create a finding?
No. LintCycle requires sufficient provider evidence and prefers no finding when correlation is uncertain.
Can repositories be selected per workspace?
Yes. Repository selection belongs to the authenticated organization and is enforced server-side.
Close the loop
Connect GitHub without handing over the controls.
Start with read-only pull-request context, then add the providers that create your preview resources.