Jordi Boggiano

I think setting packagist.org=>false in TestCase::initTempComposer inside $composerJson would probably be the better fix. I'd probably only do it if the `repositories` key is set though to avoid side effects...

Fixed the packagist.org issue in https://github.com/composer/composer/commit/a6d872191c14a00d907801c284756100d44c3f86 and rebased.

Thank you for the tests :)

No plans. I am not a fan of code coverage monitoring as I don't think it brings much value as an obsession/metric. It is quite useful here as a one-off...

I am surprised this is the first time this gets reported.. If it was a widespread Drupal issue I imagine I'd have heard of it before. So I'm guessing you're...

Gitlab Auth issues are usually not being fixed until someone sends a PR, just FYI if it's important to you maybe have a look, I believe the bitbucket code already...

Can you try to make a reproduction case in a demo git repo with the path repo and autoloading etc? Because I feel like it's probably a mistake you made...

Maybe try to patch the completion file with https://github.com/symfony/symfony/pull/47022 see if it helps you?

Right, confirmed that it needs that patch - otherwise it only seems to work if you call composer via an alias.

01a7bb8e5 fixes it for now in snapshot builds.. I'll probably delay 2.4.0 until a symfony patch release happens.