trunk
Branches trunk
1 Branches 0 Tags
Go to file T
Code
.github ci(freebsd-smoke): wire 4 W09.7 smokes + rsync pkg dep
benches L01 chunk 6 close: fanotify mark FAN_EVENT_ON_CHILD + gate goes load-bearing
crates shim: canonicalize rename(from,to) for daemon-side path matching (W09.7)
packaging fix(packaging): wrappers use --target-argv=$v (equals) not --target-argv "$v" (space)
shell fix(shell/fish): quote tty value to survive BSD tty's 'not a tty' stdout
tests smoke: rsync-incremental-undo-fbsd.sh (W09.7 — discovered rename path-canonicalization)
tools workflow(linux-kernel-capture): wire vim-edit-undo smoke + add vim-nox dep
xtask xtask: skip /vendor in license-check (third-party crates have their own licenses)
.clippy.toml S20.13 follow-up: bump clippy.toml MSRV to 1.88 to match Cargo.toml + rust-toolchain.toml (was missed in the original MSRV bump)
.gitignore S20.13 / DR-60: tools/linux-bpf-vm — Ubuntu 24.04 arm64 cloud-init provisioning under qemu+HVF; adds bpf to LSM stack via grub cmdline edit
CLAUDE.md S20.13 audit fix: bump MSRV 1.85 -> 1.88 (helper.rs uses let-chains stabilized in 1.88; pre-bump pinned toolchain wouldn't build)
CONTRIBUTING.md scaffold: license, readme, contributing, gitignore
Cargo.lock feat(shit-helper): add serde_json dep for container inspect parsing
Cargo.toml shim: per-package strip=debuginfo to preserve .gnu.version symbol map
LICENSE scaffold: license, readme, contributing, gitignore
Makefile S20.7: Makefile — tracing-leak-check grep guard (wired into make ci)
README.md scaffold: license, readme, contributing, gitignore
rust-toolchain.toml S20.13 audit fix: bump MSRV 1.85 -> 1.88 (helper.rs uses let-chains stabilized in 1.88; pre-bump pinned toolchain wouldn't build)
rustfmt.toml scaffold: cargo workspace, 8 crate stubs, xtask license-check

Contributing

This project is pre-1.0 and pre-launch. External contributions aren't open yet — we'll open up after the first stable release.

If you've spotted a bug or want to discuss an idea, open an issue at https://github.com/tenseleyFlow/shit/issues.

Security

Don't open a public issue for security findings. See SECURITY.md once published, or email the maintainer.