Skip to content

[WIP] 📌 Gemfile.lock should always be in version control #279

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

Closed
wants to merge 2 commits into from

Conversation

pboling
Copy link
Contributor

@pboling pboling commented Jul 15, 2025

Please help me support open source by sponsoring me - @pboling

@pboling pboling force-pushed the feat/278-Gemfile.lock-in-vcs branch from 2fc241d to a98e2ef Compare July 15, 2025 19:28
@pboling pboling changed the title 📌 Gemfile.lock should always be in version control [WIP] 📌 Gemfile.lock should always be in version control Jul 15, 2025
@pboling pboling marked this pull request as draft July 15, 2025 19:51
@pboling
Copy link
Contributor Author

pboling commented Jul 17, 2025

Abandoning, as maintainers have a different view of Gemfile.lock for libraries. Happy to revisit if that changes.

@pboling pboling closed this Jul 17, 2025
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.

1 participant