Files
wickra/.gitignore
T
kingchencandGitHub 3093f194a2 docs: document the repo-wide lockfile policy (P4) (#82)
The .gitignore comment claimed package-lock.json is committed only under
bindings/node/, but examples/node/package-lock.json has also been tracked
since #80. Correct the comment and add a CONTRIBUTING 'Lockfile policy'
section spelling out every component: Cargo.lock + the two Node package-locks
are tracked; fuzz/Cargo.lock is ignored (cargo-fuzz default); the Python
package has no lockfile by PyO3 convention (pinned via Cargo.lock); the
ghost-ignored site keeps its lockfile local.
2026-05-31 05:11:08 +02:00

60 lines
915 B
Plaintext

# Rust
/target/
**/target/
Cargo.lock.bak
*.pdb
# Python
__pycache__/
*.py[cod]
*$py.class
*.so
*.pyd
*.egg-info/
.pytest_cache/
.venv/
venv/
.python-version
dist/
build/
wheels/
*.whl
# Editor / OS
.idea/
.vscode/
*.swp
.DS_Store
Thumbs.db
# Maturin
target/wheels/
# Benchmarks
criterion/
# Coverage
*.profraw
lcov.info
tarpaulin-report.html
# Local config that should not be committed
*.local.toml
# Node binding artifacts
**/node_modules/
bindings/node/*.node
bindings/node/index.d.ts
bindings/node/npm-debug.log*
# package-lock.json is committed for the tracked Node packages — bindings/node/
# and examples/node/ — so contributors get reproducible npm installs. There is
# no top-level npm package, and the ghost-ignored site/ keeps its lockfile local.
# See CONTRIBUTING.md "Lockfile policy" for the full per-component breakdown.
# WASM build output
bindings/wasm/pkg/
# Python venv
.venv/
venv/