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

Move mix.lock to .gitignore #160

Open
nappex opened this issue Jan 15, 2023 · 1 comment
Open

Move mix.lock to .gitignore #160

nappex opened this issue Jan 15, 2023 · 1 comment

Comments

@nappex
Copy link
Collaborator

nappex commented Jan 15, 2023

Currently, dependencies update by $ mix deps.update change mix.lock file. Particulary, hashes of dependencies that are created by its version.
I think mix.lock should be generated locally by run commands as $ mix deps.update, it should not be created or rewritten by git pull.

@nappex nappex changed the title Move mix.lock to .gitignore Move mix.lock to .gitignore Jan 15, 2023
@Glutexo
Copy link
Owner

Glutexo commented Feb 24, 2024

The general consensus is to commit the lock file: https://duckduckgo.com/?q=should+I+commit+gemfile.lock The reasoning is that the lock file provides an environment tested to be working and that tests can be run on. If you want to bump dependencies, you can always delete the lock file locally and run deps.get yourself. The lock file provides additional information and you are free to use it or not.

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

No branches or pull requests

2 participants