Build Android artifacts with a reusable workflow#270
Build Android artifacts with a reusable workflow#270webknjaz wants to merge 2 commits intopython:mainfrom
Conversation
This is a follow up for python#265 that added initial implementation with copy-pasted steps.
|
@mhsmith here's the interface I envision. The references would need to be updated, of course. But it does still rely on the same API surface of |
|
Example in-fork GHA run: https://github.com/webknjaz/python--release-tools/actions/runs/16969209454 |
|
Thanks; I'm on holiday for the next few days, but I'll look at this when I get back. |
|
Please could you resolve the conflict to point to upstream |
|
@hugovk is that necessary at this point, while in review? The branch has a few temporary things that should not be merged anyway. |
|
Yes please, it's better if we can review it in the mergeable state, without the temporary things/FIXMEs. |
|
I'm not sure this is an improvement. See python/cpython#137768 (comment). |
The thing is that it's not really possible to point to a merge commit that doesn't exist before the PR is merged. So I don't see this happening at this stage. That's effectively why I created this PR as a draft. But that doesn't matter anymore since it looks I'll have to abandon the cross-repo reusability bit for now. |
This is a follow up for #265 that added initial implementation with
copy-pasted steps.