Closed mattrobmattrob closed 10 months ago
seems fine for now but this looks to go against what's suggested here: https://bazel.build/external/lockfile
Include the lockfile in version control to facilitate collaboration and ensure that all team members have access to the same lockfile, promoting consistent development environments across the project.
seems fine for now but this looks to go against what's suggested here: https://bazel.build/external/lockfile
Include the lockfile in version control to facilitate collaboration and ensure that all team members have access to the same lockfile, promoting consistent development environments across the project.
I'm following https://github.com/bazelbuild/rules_swift/commit/d0687c3c9957633376a7099d03e0ced183f64f75 for now. IMO, it's probably a different rationale for rulesets vs. normal repos but 🤷
Ah that's fair
This file is generated by default by bazel @ HEAD but we don't really want to manage it. This way it can be generated locally and folks can build offline if they have generated it at least once.