Skip to content

fix: rename env.example back to .env.example, add .gitignore - #8

Merged
emnl51 merged 1 commit into
mainfrom
fix/env-example-naming
Aug 6, 2026
Merged

emnl51 merged 1 commit into
mainfrom
fix/env-example-naming

Conversation

@emnl51

@emnl51 emnl51 commented Aug 6, 2026

Copy link
Copy Markdown
Owner

#5 renamed .env.example to env.example (dropped the leading dot), which broke the standard convention most tooling and copy-paste habits rely on. The new required vars (SANDBOX_SERVICE_TOKEN, VECTOR_SERVICE_TOKEN, REPUTATION_SERVICE_TOKEN, DEVELOPER_TOKEN_SIGNING_SECRET) never propagated to local .env files as a result. Renamed back and added a .gitignore so a real .env is never accidentally committed.

env.example (no leading dot) was silently missed by tooling/convention
that expects .env.example, so the new SANDBOX_SERVICE_TOKEN /
VECTOR_SERVICE_TOKEN / REPUTATION_SERVICE_TOKEN /
DEVELOPER_TOKEN_SIGNING_SECRET vars introduced in #5 never made it
into anyone's local .env. Renamed back, and added .gitignore so a
real .env is never committed going forward.
@bolt-new-by-stackblitz

Copy link
Copy Markdown

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@emnl51
emnl51 merged commit 2b149b7 into main Aug 6, 2026

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

馃挕 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 36655a18cc

鈩癸笍 About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 馃憤.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread .gitignore
Comment on lines +2 to +4
dist/
.next/
.turbo/

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Untrack generated artifacts when adding ignore rules

Ignoring these directories does not affect files already tracked in the index. In the reviewed tree, 108 dist, 214 .next, and 294 .turbo files remain tracked, so subsequent builds will continue to expose their changes in git status and allow generated output to be committed. Remove the existing artifacts from the index as part of this change.

Useful? React with 馃憤聽/ 馃憥.

Comment thread .gitignore
.turbo/
*.log
.env
.env.*.local

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Ignore the standard .env.local file

For developers running the Next.js web app with overrides or credentials in apps/web/.env.local, this pattern does not match .env.local (it only matches names such as .env.development.local). The file therefore remains eligible to be staged and committed, undermining the stated protection against leaking local environment values; add an explicit rule or ignore .env* while exempting .env.example.

Useful? React with 馃憤聽/ 馃憥.

@emnl51
emnl51 deleted the fix/env-example-naming branch August 6, 2026 20:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants