It's not infrequent that, when trying to merge upstream updates where the composer.json file has changed, that using the checkbox for Pantheon to "automatically merge" the upstream update diffs will result in most of your composer.json being wiped out in a Composer Managed-based upstream. This is relatively easy to resolve since, locally, you'll usually have the last working copy of the composer file to just re-apply, but this should be documented.
How will this impact users?
Give users additional guidance about what to do when this situation occurs. It can be alarming when all of your packages (and indeed, basically your entire composer project) disappears.
Suggested Resolution
The fix is to back up your composer.json file before you do a git pull if you see this in your dashboard. Once you do a git pull, you can simply delete the composer.json from the site repo, add your own, and locally run a composer update
Re: Create a Composer-managed WordPress Site with Bedrock
Priority: Medium
Issue Description
It's not infrequent that, when trying to merge upstream updates where the composer.json file has changed, that using the checkbox for Pantheon to "automatically merge" the upstream update diffs will result in most of your
composer.jsonbeing wiped out in a Composer Managed-based upstream. This is relatively easy to resolve since, locally, you'll usually have the last working copy of the composer file to just re-apply, but this should be documented.How will this impact users?
Suggested Resolution
composer.jsonfile before you do a git pull if you see this in your dashboard. Once you do a git pull, you can simply delete the composer.json from the site repo, add your own, and locally run acomposer update