Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • Short answer: Yes, commit composer.lock. There are reasons to not commit it, but if you're reading this question, they probably don't apply to you.
    – rinogo
    Commented Oct 8, 2020 at 19:21
  • If your composer.lock is not in .gitignore, first : add it to .gitignore file, second : delete this file from repository, end : pull from repository. In this case, composer.lock committed to repository before. When there is file in repository, you can not ignore it, and so must be commit its changes.
    – Mehdiable
    Commented Dec 20, 2021 at 10:22