Closed jaapio closed 2 months ago
This needs a rebase and a conflict needs to be fixed due to one of the past PRs introduced changes to composer.lock. Has anyone used the "Resolve conflicts" button of GitHub? I was quite tempted to use it, but I rather prefer to do such steps in a console.
I remember trying it in the past, but I usually stick to the console, and would certainly do so for composer.lock
. That being said, there's a chance @jaapio allows writing to his branch, so you could try fixing it locally. I'll give it a try.
Yup, writable, that's usually the case. I use https://ldez.github.io/prm/ for this, but I think gh
also covers this feature.
The logger introduced before was very usefull in the setup process but by now, it should be replaced by something more mature to ensure the logs to not end up in the final output.