bart

> I think, to preserve backwards compatibility, the long-term path forward is probably two different options (in my example, `supplemental` and `private`). I would propose something like the following, as...

Hi all, I spend most of my last two days looking into this issue and I found a (temporary) solution for this. The issue that you describe is caused by...

It appears that our bots DO have emails, but the API call was limited. The following yields an email address: `curl -s --request GET --header "PRIVATE-TOKEN:" "${CI_API_V4_URL}/user" | jq '.email'`...

Yep, adding the following snippet to the script solves my problem without need for repo configuration changes: ```yaml script: - export GIT_COMMITTER_EMAIL=$(curl -s --request GET --header "PRIVATE-TOKEN:$GL_TOKEN" "${CI_API_V4_URL}/user" | jq...

> #6669 represents incremental progress towards this goal, and the author is interested in implementing this proposal. Indeed I am. The refactor is "hairy" (not my words), but it appears...

I've made a [draft PR](https://github.com/python-poetry/poetry/pull/6879) to facilitate the discussion. High-level feedback is very welcome (may save future revisions)!

We regularly use an internal mirror with fallback to PyPI. Our packages are developed internally and made public with some delay (and not all versions are released externally). During development...

> `secondary = true` would be kept around as a deprecated option (likely with a warning), and would maintain the legacy behavior of being searched exhaustively for backwards compatibility. @neersighted...

Thank you for the detailed overview and proposal. Perhaps the one thing that can be clarified is what the resolution order implies (perhaps also to add to the docs in...

Friendly reminder to @ericwb, @lukehinds and/ or @sigmavirus24 for considering this PR.