Skip to content

Conversation

@browner12
Copy link
Contributor

do not commit the composer lock file.

when forking and updating the repo, users run composer update to get the latest dependencies. this creates a composer.lock file that we don't want committed back to the package repo.

similar to other Laravel packages that don't commit the lock file.

https://github.com/laravel/horizon/blob/2.0/.gitignore
https://github.com/laravel/tinker/blob/master/.gitignore

do not commit the composer lock file.

when forking and updating the repo, users run `composer update` to get the latest dependencies. this creates a `composer.lock` file that we don't want committed back to the package repo.

similar to other Laravel packages that don't commit the lock file.
@driesvints
Copy link
Member

Thanks but we'll have to remove the composer.lock file first.

@driesvints driesvints closed this Feb 26, 2019
@driesvints driesvints reopened this Feb 26, 2019
@driesvints driesvints merged commit f541c30 into laravel:master Feb 26, 2019
@driesvints
Copy link
Member

Deleted it. Thanks!

@browner12 browner12 deleted the ignore-composer-lock branch February 26, 2019 22:09
@browner12
Copy link
Contributor Author

thanks for catching that!

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.

2 participants