Neon
Cost
Releases
Branch created in PR workflow with no delete-on-close
Part of the Branching & migrations check · fix arrives as a guide
What it is
A CI workflow creates a Neon branch per pull request but has no step deleting it when the pull request closes.
Why it matters
Every PR leaves a branch behind holding its own compute and storage. Nothing about any individual branch looks expensive, which is exactly why the total goes unnoticed for months.
How to fix it
Add a workflow on the closed pull request event that deletes the branch, or set an expiry when creating it so cleanup happens even if the workflow does not run.
Run them all on your app
Connect your repo and your live services with read-only scopes. The first scan is free, and nothing changes without your approval.