chore: stop tracking .env file #9

Merged

julian merged 1 commit from chore/untrack-env-file into main

2026-06-14 17:17:07 +02:00

julian commented

2026-06-14 17:16:41 +02:00

Owner

What

Untrack .env so local environment secrets stay out of version control.

Why

.env is listed in .gitignore (line 34) but was committed earlier as an empty file, so the ignore rule never took effect. The file has since accumulated local secrets (a Forgejo API token), which must not be versioned. This runs git rm --cached .env — the local file is kept, and since the prior tracked version was empty, no secret enters git history.

Notes

This surfaced while fixing the post-rename iOS build (stale CocoaPods paths, module caches, and a zombie Metro server). Those fixes all live in the gitignored ios//android/ native dirs (regenerated from app.json), so they are not part of this or any commit.

🤖 Generated with Claude Code

## What Untrack `.env` so local environment secrets stay out of version control. ## Why `.env` is listed in `.gitignore` (line 34) but was committed earlier as an empty file, so the ignore rule never took effect. The file has since accumulated local secrets (a Forgejo API token), which must not be versioned. This runs `git rm --cached .env` — the local file is kept, and since the prior tracked version was empty, no secret enters git history. ## Notes This surfaced while fixing the post-rename iOS build (stale CocoaPods paths, module caches, and a zombie Metro server). Those fixes all live in the gitignored `ios/`/`android/` native dirs (regenerated from `app.json`), so they are not part of this or any commit. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

julian added 1 commit

2026-06-14 17:16:41 +02:00

chore: stop tracking .env file 3bb1ecd0c8

.env is listed in .gitignore but was tracked from an earlier empty
commit, so the ignore rule never applied. Untrack it (git rm --cached)
so local environment secrets stay out of version control.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>