-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MODULE.bazel.lock change not included in PRs #422
Comments
Perhaps this is happening when it fails to run I originally had some Those are now fixed, but I think it's now failing due to #424, and perhaps that's the root cause of this. Should it perhaps be more robust and skip some of these error and still commit and proceed? |
Actually, no. So what happens is that when
Probably not, actually; it's likely better for this to be noticed.
I've now cleaned everything up as much as possible, see e.g. this run, but the It's doing This does seems like a bug, to me. |
enola-dev/enola#1175 and enola-dev/enola#1176 don't include
MODULE.bazel.lock
.Should this "just work" out of the box? Or is there any configuration needed for this?
The text was updated successfully, but these errors were encountered: