Remove Gemfile.lock when running CI on Ruby 3.1 Windows #163
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vinistock
force-pushed
the
vs/remove_gemfile_lock_on_31_windows
branch
from
c98c5e1 to
f545e8e
Compare
andyw8
approved these changes
Sep 26, 2023
|
I'm wondering if this will affect the bundle caching and possibly slow things down - we'll see once it's on |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It has proved impossible to get CI to work without removing the Gemfile.lock. Let's remove it only for Ruby 3.1 on Windows, so that our auto-merge continues to work.