Salesforce-Separation-Of-Concerns-And-The-Apex-Common-Library/.gitignore at main · Coding-With-The-Force/Salesforce-Separation-Of-Concerns-And-The-Apex-Common-Library · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
# ── Node / Docusaurus ────────────────────────────────────────────
# Unanchored, so a second package directory is covered without an edit.
# node_modules is ~32,000 files; npm ci rebuilds it exactly from the
# committed package-lock.json, which is why the lockfile IS tracked.
node_modules/
.docusaurus/
.cache-loader/

# Build output. Anchored, because "build" is a generic enough name that an
# unanchored rule could swallow something under src/ later.
website/build/

# package manager noise
npm-debug.log*
yarn-debug.log*
yarn-error.log*
.pnpm-debug.log*
.pnpm-store/
.yarn/*
!.yarn/patches
!.yarn/releases
!.yarn/plugins
!.yarn/sdks
!.yarn/versions
.pnp.*

# TypeScript incremental build cache
*.tsbuildinfo

# ── Secrets ──────────────────────────────────────────────────────
# Nothing here today, but a Salesforce repo is exactly where an auth
# file or a scratch-org key eventually gets dropped by accident.
.env
.env.*
!.env.example
*.pem
*.p12
server.key
jwt/

# ── Salesforce ───────────────────────────────────────────────────
.sfdx/
.sf/
.localdevserver/
deploy-options.json
.apexcodecoverage/
*.log

# ── Editors ──────────────────────────────────────────────────────
.idea/
*.iml
*.ipr
*.iws
.vscode/
!.vscode/extensions.json
!.vscode/settings.json
!.vscode/launch.json

# ── OS ───────────────────────────────────────────────────────────
.DS_Store
.DS_Store?
._*
.Spotlight-V100
.Trashes
Thumbs.db
ehthumbs.db
desktop.ini