Untracked MODULE.bazel.lock files
#223
Comments
|
Let's opt for ignore the files. IIRC, I read through an github issue or discussion that mention it but cannot find it again. It mentions that the lock file is not quite stable at the moment, and needs some refine on it. So lets ignore it for now and keep an eye on it. |
|
Sounds good to me. Created #224 BTW, I saw github issue in bazel repo bazelbuild/bazel#20369, not sure if that was what you saw. |
neilconway
added a commit
to neilconway/stout
that referenced
this issue
Dec 23, 2024
There seems to be some debate about whether to add these files to git or ignore them (e.g., [1]). For now, let's ignore them. [1] bazel-contrib/rules_cuda#223
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
bzlmod will automatically generate
MODULE.bazel.lockfiles, but this file is neither tracked by git nor placed in .gitignore file, causing every time git to alertMODULE.bazel.locknot being tracked, and adds to chance that this file is committed inadvertently. IMO it could be a quite simple fix by choosing either of the options:MODULE.bazel.lockfiles, if we are sure that this file is consistent across different machines (theoretically the lock file should maintain consistent on different machines, but I am not sure if there are any non-hermetic factors would cause environment-dependent contents).MODULE.bazel.lockfile into.gitignore, if we are unsure if the lock file would be consistent.I would be happy to provide PR if either of the above options is a way to move forward.
The text was updated successfully, but these errors were encountered: