Skip to content
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

Don't re-write an identical lockfile #2386

Merged

Conversation

illicitonion
Copy link
Collaborator

#1910 has a workaround for this because changing the timestamp may invalidate the repository rule.

Instead, just don't do the write if the contents is identical.

bazelbuild#1910 has a workaround for
this because changing the timestamp may invalidate the repository rule.

Instead, just don't do the write if the contents is identical.
@illicitonion illicitonion marked this pull request as ready for review January 2, 2024 13:31
Copy link
Collaborator

@UebelAndre UebelAndre left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great thinking!

@illicitonion illicitonion enabled auto-merge (squash) January 2, 2024 15:37
@illicitonion illicitonion merged commit 72a1818 into bazelbuild:main Jan 2, 2024
3 checks passed
@illicitonion illicitonion deleted the avoid-noop-lockfile-overwrites branch January 2, 2024 16:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants