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

Why do we need ignore composer.lock ? #4

Open
tucq88 opened this issue Nov 15, 2016 · 1 comment
Open

Why do we need ignore composer.lock ? #4

tucq88 opened this issue Nov 15, 2016 · 1 comment

Comments

@tucq88
Copy link

tucq88 commented Nov 15, 2016

As the title, I pretty confuse why your build have that check. By that, build may install different packages that ran in local => may cause random bug

@modess
Copy link
Owner

modess commented Nov 17, 2016

You do not need to have the lock file ignored in your repository. The tool will check if the lock file is ignored in your .gitignore. The steps it performs are:

  • Is composer.lock ignored in .gitignore?
    • No
      • run composer install
    • Yes
      • remove composer.lock (from previous run)
      • run composer update

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