-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy path.gitignore
More file actions
92 lines (80 loc) · 2.87 KB
/
Copy path.gitignore
File metadata and controls
92 lines (80 loc) · 2.87 KB
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
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
# Build output
[Bb]in/
[Oo]bj/
[Dd]ebug/
[Rr]elease/
x64/
x86/
[Ww][Ii][Nn]32/
[Aa][Rr][Mm]/
[Aa][Rr][Mm]64/
# Visual Studio
.vs/
*.user
*.suo
*.userosscache
*.sln.docstates
*.userprefs
# Rider / VS Code
.idea/
.vscode/
# NuGet
*.nupkg
*.snupkg
packages/
project.lock.json
project.assets.json
# Secrets — API keys for the AI extraction feature, used in development and testing.
# Never commit these. .env.example carries the variable names with no values.
.env
.env.*
!.env.example
*.key
appsettings.*.local.json
# Vendor programming guides kept as a local reference, and the web pages and forum threads
# archived while hunting for them. Free to download from the vendor, which is not a licence
# to redistribute — so a local collection lives here and stays here. More so for the forum
# threads: those are their authors' words, not the vendors'.
#
# The two committed files in this folder are the indexes — README.md for the guides,
# ARCHIVED-PAGES.md for the saved pages. The guides and pages themselves never are.
#
# At any depth, not just the top: the guides are now filed under a folder per manufacturer,
# and `datasheets/*.pdf` matches one level only — moving them into those folders would have
# quietly un-ignored all of them.
datasheets/**/*.pdf
datasheets/**/*.zip
datasheets/**/*.html
# scpi-extract working files. The pipeline's inputs and intermediates, not its output:
# manuals/ holds the pdftotext dumps of vendor guides (same reason the PDFs are ignored
# above), parsed/ and built-*.json are regenerated from those in one command. What is
# committed is cfg/<family>.json — the recipe — and the catalog it produces in
# Core/CommandData/.
tools/scpi-extract/manuals/
tools/scpi-extract/parsed/
tools/scpi-extract/built-*.json
# Test run artefacts
Tests/TestResults/
# The SDK writes a launch profile for the WebAssembly client the first time it is built,
# carrying a port it picked at random on that machine. The client is never launched on its
# own — the server hosts it — so the file is noise that differs per checkout. The server's
# own launch profile is committed and must stay that way: without it the app starts in
# Production, where the Blazor static assets are not wired up and every one of them 404s.
Web/LabEquipmentController.Web.Client/Properties/launchSettings.json
# Misc
*.log
*.tmp
[Tt]humbs.db
.DS_Store
# Local editor and agent scaffolding: a launch config for the web app, not part of the build.
.claude/
bench-reports/
# tools/sample-catalog-accuracy.js writes here; the sample is reproducible from its seed
sample.json
# Playwright end-to-end tests for the web client. The specs are committed; what npm and the
# browser leave behind is not — including the server's isolated data directory, which exists
# so a run cannot read or write the settings a real session saved.
Web/tests/node_modules/
Web/tests/test-results/
Web/tests/playwright-report/
Web/tests/.data/