Skip to content

chore: remove duplicate env sample file - #416

Merged
birme merged 1 commit into
mainfrom
chore/remove-duplicate-env-sample-file
Oct 20, 2026
Merged

birme merged 1 commit into
mainfrom
chore/remove-duplicate-env-sample-file

Conversation

@Saelmala

Copy link
Copy Markdown
Contributor

A second env.sample file had been added (called env.example).
This PR keeps the variables only existing in the new file, but puts them in the first sample env file.

@Saelmala Saelmala self-assigned this Oct 20, 2026
@Saelmala
Saelmala requested a review from birme as a code owner October 20, 2026 11:17

@birme birme left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Reviewed by the daily-backlog-pr Phase 3.5 orphan-PR housekeeping pass (independent code-reviewer invocation, extra scrutiny for an external contributor).

Verdict: LGTM. The diff matches the stated scope exactly:

  • .env.example deleted (duplicate); all 23 variables folded into .env.sample with none dropped.
  • .gitignore drops the now-obsolete !.env.example negation.
  • src/server.ts change is comment-only (.env.example → .env.sample); validateRequiredEnv() logic untouched.

Security: every sample value is a placeholder (localhost/empty/turn:user:pass@turn.example.com) — no real secrets, no backdoor, no weakened validation, no scope creep. CI (lint, prettier, typecheck, unit tests) green.

@birme
birme merged commit b8b51ab into main Oct 20, 2026
4 checks passed
@birme
birme deleted the chore/remove-duplicate-env-sample-file branch October 20, 2026 11:41
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