-
Notifications
You must be signed in to change notification settings - Fork 2
Expand file tree
/
Copy path.gitignore
More file actions
120 lines (101 loc) · 3.1 KB
/
Copy path.gitignore
File metadata and controls
120 lines (101 loc) · 3.1 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
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
# Build artifacts
/target/
/tmp-*/
**/*.rs.bk
**/compile_commands.json
# Staged binary copied into the wheel by setup.py's BuildWithCargo cmdclass
# (#423). Source is target/release/fbuild[.exe]; never check the staged
# copy in.
/ci/bin/
# IDE
.idea/
.vscode/
*.swp
*.swo
*~
# OS
.DS_Store
Thumbs.db
# Runtime DLLs (copied at runtime, not shipped in repo)
libiconv-2.dll
# Session cache (hook fingerprints)
.cache/
# zccache local dev cache
.zccache/
# fbuild local build artifacts
.fbuild/
.pio/
benchmark-output/
benchmark-stats/
tests/platform/*/build_info*.json
# Local cargo cache
.cargo/.global-cache
.cargo/.package-cache
.cargo/.package-cache-mutate
.cargo/git/
.cargo/registry/
# Same caches, at any depth. The patterns above contain a slash, so git
# anchors them to the repo root and they do NOT cover nested crates.
# Running any cargo command inside `dylints/<lint>/` (each is its own
# workspace with its own `.cargo/config.toml`) materializes a full registry
# cache there — thousands of vendored files that a `git add -A` will happily
# stage.
**/.cargo/.global-cache
**/.cargo/.package-cache
**/.cargo/.package-cache-mutate
**/.cargo/git/
**/.cargo/registry/
# Cargo lock is checked in for binaries
# (workspace contains binary crates)
.loop
# Python / uv
__pycache__/
*.pyc
*.pyo
.venv/
*.egg-info/
dist/
build/
# PyO3 native extension — built locally from crates/fbuild-python via
# `uv run cargo build --release -p fbuild-python --features extension-module`,
# then copied into python/fbuild/. Never commit these binaries: they go stale
# relative to crates/fbuild-python/src/lib.rs and break Python tests with
# ModuleNotFoundError / AttributeError. CI rebuilds them on every publish.
python/fbuild/_native.pyd
python/fbuild/_native.abi3.so
python/fbuild/_native.so
python/fbuild/_native.dylib
# VSCode extension build artifacts
vscode-fbuild/out/
vscode-fbuild/node_modules/
vscode-fbuild/*.vsix
.claude/worktrees/
.claude/scheduled_tasks.lock
/bin/
# Local agent-loop scratch — LOOP.md is an operator-driven benchmark spec
# generated per-session; not a stable doc and not part of the repo.
/LOOP.md
tasks/loop-runs/
# Local staging dir for the orphan `online-data` branch's tooling.
# The actual files live on that branch only — see
# `.github/workflows/nightly-usb-ids.yml` and `docs/online-data.md`.
.online-data-staging/
# `git worktree add` location used by the nightly workflow.
.online-data/
# Cross-repo checkouts created by the `clud-extern-repos` skill —
# dependent-repo clones that live here only for the duration of a
# multi-repo change. Each subdir is its own independent git repo and
# must never be committed into fbuild.
.extern-repos/
# clud project settings
!.clud/
!.clud/settings.json
.claude/tmp/
# `fbuild port scan` ad-hoc diagnostic captures (added with PR #741).
# Users sometimes redirect stderr/stdout to inspect the device list;
# the captures are local-only and should never be checked in.
port_scan_stderr*.txt
port_scan_stdout*.txt
# Profiling harness artifacts (FastLED/fbuild#942) - local-only measurement
# output: flamegraphs, perf.data, daemon logs, timing tables.
ci/docker-profile/out/