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

Track composer.lock #250

Merged
merged 1 commit into from
Feb 13, 2022
Merged

Conversation

itinerare
Copy link
Collaborator

@itinerare itinerare commented Feb 1, 2022

The composer.lock file should really be tracked, as it helps ensure consistency of package versions and reduces the amount of variance, for instance helping for any issues arising from diff dependency versions to be more easily tracked and resolved... Even for sites with different packages, standardizing tracking it across the board helps ensure their local and live environments are using the same versions of packages, etc.

I've run composer update prior to committing, so should be appropriately representative of the current state of develop's dependencies

@itinerare itinerare added the needs review Pull requests that are pending community review label Feb 1, 2022
@itinerare itinerare added reviewed Pull requests that have received community review and are pending merge and removed needs review Pull requests that are pending community review labels Feb 13, 2022
@itinerare itinerare merged commit d8b78f2 into corowne:develop Feb 13, 2022
@itinerare itinerare deleted the feature/track-lock-file branch February 13, 2022 03:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
reviewed Pull requests that have received community review and are pending merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants