sneak
96924d8dc9
check / check (push) Successful in 28s
The comment said a committed template is re-included by a negation, but the file re-includes only `example.env` and `sample.env`. It now names those two and tells a repository to add its own negation after these lines for any other template, for example `!.env.example`, as the `.dockerignore` comment does. Model: opus-5-5
46 lines
1.1 KiB
Plaintext
46 lines
1.1 KiB
Plaintext
# OS
|
|
.DS_Store
|
|
Thumbs.db
|
|
|
|
# Editors
|
|
*.swp
|
|
*.swo
|
|
*~
|
|
*.bak
|
|
.idea/
|
|
.vscode/
|
|
*.sublime-*
|
|
|
|
# Agent scratch (worktrees of this repo, created and destroyed by
|
|
# in-flight tooling). Unanchored: .gitignore patterns already match at
|
|
# every depth, so no prefix is wanted here. This is not a .dockerignore
|
|
# entry and must not be given a `**/` prefix on the way into one.
|
|
.claude/
|
|
|
|
# Node
|
|
node_modules/
|
|
|
|
# Secrets. Unanchored like every entry above, so each matches at every
|
|
# depth. Matching is case-sensitive on Linux, so names use character
|
|
# ranges rather than a lowercase form that misses `Server.Key`.
|
|
|
|
# Environment files. `*.env` covers bare `.env` and the `prod.env`
|
|
# convention. Only the templates `example.env` and `sample.env` are
|
|
# re-included below. A repository that commits any other template adds
|
|
# its own negation after these lines, for example `!.env.example`.
|
|
*.[eE][nN][vV]
|
|
.[eE][nN][vV].*
|
|
.[eE][nN][vV][rR][cC]
|
|
!example.env
|
|
!sample.env
|
|
|
|
# Private keys and the bundles carrying them.
|
|
*.[pP][eE][mM]
|
|
*.[kK][eE][yY]
|
|
*.[pP]12
|
|
*.[pP][fF][xX]
|
|
[iI][dD]_[rR][sS][aA]
|
|
[iI][dD]_[dD][sS][aA]
|
|
[iI][dD]_[eE][cC][dD][sS][aA]
|
|
[iI][dD]_[eE][dD]25519
|