I think anything we can do to make their life easier is great.

Totally reasonable proposal, and I'm happy to do the refactoring or review PRs for it!

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:

- name: Delete older wheel uploads
  uses: scientific-python/upload-nightly-action/.github/workflows/remove-wheels.yml@main

or is the plan to publish two separate workflows per release so that they can be called with scientific-python/upload-nightly-action/[email protected]? 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 as N_LATEST_UPLOADS and ANACONDA_USER as configurable inputs to the step above (with with:) 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!).