Jordi Boggiano

@dzuelke yeah I think that all sounds great, it would mirror a bit the git remote command I guess (+ ordering..). Definitely would be more sensible than adding more hacks...

Thanks @JoshuaBehrens again, this is great work. I did tweak some things in the few commits above but I think now we're in a pretty good spot with this! Only...

@JoshuaBehrens if you want to do canonical/only/exclude feel free put please work on a new PR based on this one, as I'd rather get this one merged already. The newline...

That sounds sensible.. @JoshuaBehrens if you have time for this be my guest 😇

Yeah you ideall convert repos to an array, remove the keys and move them to name properties then you can use the new repo command with it all

Yeah this sounds very possible that it is caused by concurrency and blocking prompts. I've never caught this as I always have a single remote repo, but it makes sense...

Afterer having a chat with @WyriHaximus about this, I guess the only way forward is to retry requests that timed out during a blocking prompt.. I'm not yet sure how...

I had a chat with @TimWolla because it seemed weird to me that LOCK_UN requires a return value check as well.. Conclusion from the discussion is: - flock(..., LOCK_UN) technically...

See https://github.com/composer/getcomposer.org if you wanna contribute some styling improvements (just please don't go overboard :) incremental is the way to go)

@maxbeckers could you add support for CTRL-C as well here or is that another problem? See https://github.com/composer/composer/issues/12106 for example.