Skip to content

Clarify when copying .env files is safe #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Clarify when copying .env files is safe #9

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 13 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -334,8 +334,19 @@ gtr config add gtr.copy.exclude "**/.env"
gtr config add gtr.copy.exclude "**/secrets.*"
```

> [!WARNING]
> Be careful not to copy sensitive files. Use `.env.example` instead of `.env`.
#### Security Best Practices

**The key distinction:** Development secrets (test API keys, local DB passwords) are **low risk** on personal machines. Production credentials are **high risk** everywhere.

```bash
# Personal dev: copy what you need to run dev servers
gtr config add gtr.copy.include "**/.env.development"
gtr config add gtr.copy.include "**/.env.local"
gtr config add gtr.copy.exclude "**/.env.production" # Never copy production
```

> [!TIP]
> The tool only prevents path traversal (`../`). Everything else is your choice - copy what you need for your worktrees to function.

### Hooks

Expand Down