ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Bazel enforces strict action sandboxing, requiring every build action to explicitly declare all inputs and outputs, eliminating non-determinism caused by implicit environment dependencies.
Lock the dependency resolution with composer.lock and install exactly those versions. Use composer install, not update, in CI and production for deterministic PHP builds.
Commit the exact NuGet restore graph with packages.lock.json to prevent transitive dependency drift across developers and CI for .NET projects.
Build a reproducible SVGO pipeline using declarative plugin order, isolated testing, and optional multipass convergence with clear checks and rollback.
Commit composer.lock for apps and run composer install in CI. Update locally to move constraints, install everywhere else to reproduce the exact dependency graph with Composer 2.
bazel
composer
dotnet
svgo