Repository navigation
Conversation
Link the production branch in a gitignored .neon file and declare the starter neon.ts policy. Connection strings stay out of the repo until a signed-in deploy writes .env.local. Co-authored-by: pschmeln <pschmeln@users.noreply.github.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
neon initlinked this repo to the existing Neon project and production branch and wrote the starterneon.tspolicy plus the@neon/configand@neon/envpackages..neonandnode_modules/are gitignored. No connection string is in this diff.Deploy and app wiring are still blocked. The Neon CLI is waiting on a browser sign-in on this agent's desktop. After that sign-in, the next step is
neon deploy(which writes.env.local) and using those variables in the app from the Neon agent skills..env.localmust stay untracked.Acceptance criteria
Gaps:
neon deployhas not written.env.local.How to review
Read
neon.ts,package.json, and the.gitignoreadditions. Confirm the diff has no.env,.env.local, or.neonfile and no connection string.Ran
python3 scripts/check_workflow.py(Workflow scaffolding OK).Isolation
cursor/neon-connection-aac5Secrets
Handoff
Branch:
cursor/neon-connection-aac5. Done: Neon CLI setup, project link, and starterneon.ts. Remains: finish the Neon browser sign-in, runneon deploy, then use the pulled variables in app code. A human starts the next session. Paste: finish the Neon sign-in already open on the agent desktop, then continueneon deployand wire the app without printing connection strings.Merge
A human merges. Agent instructions and this checklist leave the merge button available until an admin enables branch protection or a ruleset.