Repository navigation
Make Remove Old Wheels workflow seperate GitHub Action #62
Description
As we're getting requests from different libraries to be added (Issues #29, #45, #50) and recommending to those groups to instead make their own Anaconda Cloud org and use the 0.3.0 release of the action to upload to their own org (#47 (comment), scikit-hep/awkward#3011) it would be nice to also not have these teams have to reimpliment their own space saving workflow.
It would be easy to turn the "Remove old wheels" workflow into a YAML only (no Docker needed) GitHub Action to pair with the upload-nightly-action.
Thoughts?
Reacted by Brigitta Sipőcz, Jarrod Millman and Agriya Khetarpal
Activity
stefanv commentedon Feb 8, 2024
I think anything we can do to make their life easier is great.
bsipocz commentedon Feb 8, 2024
Totally reasonable proposal, and I'm happy to do the refactoring or review PRs for it!
agriyakhetarpal commentedon Mar 22, 2024
Hi! I'm willing to help out by writing a PR for this, but I would love some pointers as to how to start – one of the reasons why I ask this is because isn't it easy for someone to run a workflow from a file, i.e., just run https://github.com/scientific-python/upload-nightly-action/blob/main/.github/workflows/remove-wheels.yml inside another workflow? i.e., something like:
or is the plan to publish two separate workflows per release so that they can be called with
scientific-python/upload-nightly-action/remove-wheels@vX.Y.Z? I am an avid user of GitHub Actions and I'm pretty familiar with the syntax by now – but it would be the first time writing one myself :) I did glance at the code briefly – I assume what one needs to do is to provide things asN_LATEST_UPLOADSandANACONDA_USERas configurable inputs to the step above (withwith:) where the workflow will be used (also, it might make sense to map these environment variables to the context of a specific step where their use is invoked instead of the entire job). I would be happy to receive further clarifications (and add this feature, if you don't intend to work on it at this time, that is, @bsipocz – please let me know!).