1

I'm working on a Composer-managed project with git. I merged in some changes from other folks and got a merge conflict on the composer.lock file.

Once I have manually edited the file to resolve the conflict, is there a way I can test Composer before committing my changes, without actually updating anything?

Improve this question

1 Answer 1

Reset to default
2

Yes, performing a composer install will install exactly the package versions from the composer.lock without updating to any newer version.

To test without changing composer install --dry-run will output the operations but will not execute anything.

Improve this answer
2
  • Thanks! Also I found the --dry-run option which avoids changes
    – NoChecksum
    Commented Nov 17, 2015 at 15:24
  • Yes of course you can use the --dry-run parameter. Added it to the answer.
    – Pᴇʜ
    Commented Nov 17, 2015 at 15:30

Not the answer you're looking for? Browse other questions tagged or ask your own question.