🧪 Sync reusable-cibuildwheel.yml w/ upstream#1193
Conversation
This is in line with the global unification effort.
CodSpeed Performance ReportMerging #1193 will degrade performances by 26.04%Comparing Summary
Benchmarks breakdown
|
ce4424d to
0f49f9f
Compare
0f49f9f to
e0aeedf
Compare
e0aeedf to
08ba072
Compare
08ba072 to
525c1c1
Compare
525c1c1 to
68b14b4
Compare
|
@webknjaz could you wait for tomorrow please. |
|
I don't need a review, really. It's thing I'll be hosting outside aio-libs, eventually. This is to ease the migration. |
68b14b4 to
e5e92b9
Compare
e5e92b9 to
0072f7e
Compare
It scares me a little. Is there any chance of having write access to these outside things for aio-libs admins? |
|
It's going to be PyPA so no. But I'm not migrating just yet. I need to solve a few things and document usage strategies. |
What do these changes do?
This is an infra change that generalizes the
cibuildwheelworkflow as a part of preparation to my effort of further extraction externally.This includes having input names in line with
reusable-tox.ymland configuringcibuildwheelvia env vars passed through inputs.Are there changes in behavior for the user?
Nope.
Related issue number
N/A
Checklist