Remove Gemfile.lock and .ruby-version from repository #62
Conversation
This file contains hidden or 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
a2ikm
force-pushed
the
ignore-gemfile-lock-and-ruby-version
branch
from
b98c004 to
8537899
Compare
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.
This pull request removes
Gemfile.lockand.ruby-versionfrom the repository, and adds them to.gitignore.Since this is a gem project (not an application), we shouldn’t lock dependencies or Ruby versions. Maintaining these files would unnecessarily restrict compatibility and make it harder for contributors and users to install the gem under different environments.
Dependency installation is already verified through CI, ensuring that all required gems can be installed successfully.