Allow a new inputs parameter named anaconda_nightly_upload_url

[skoudoro]

Hi Scientific Python Team,

is it possible to add the optional input anaconda_nightly_upload_url.

Instead of creating a different fork, I would like to reuse this action for another anaconda repo (DIPY nightly wheels)

it would be great to have also the optional input label (manage anaconda label).

Let me know what you think, if it is possible to do that here or if I should fork and maintain an alternative version.

thank you for the feedback.

[stefanv]

This sounds reasonable; and can be made optional so it won't impact current use. People may (will 😂) have opinions about the naming, but that can be discussed in the PR.

[matthewfeickert]

I had originally raised this idea in Issue #8, but it was decided to not go forward with it for the reasons discussed there.

I would be in favor of this, but before opening a PR let's ping @betatim and @bsipocz to see if they have different views now.

[stefanv]

From that discussion, it wasn't clear there was an existing use-case. Also, it didn't look like @betatim or @bsipocz had strong reservations.

[bsipocz]

I would fully support this feature, the more packages using the action the better it is for the ecosystem. (My only reservations in the past was about the SP anaconda space and therefore to limit it to core libraries, or at least test it in practice and preferably work out policies before opening it up for domain packages)

[bsipocz]

People may (will 😂) have opinions about the naming, but that can be discussed in the PR.

fwiw, I like the suggested anaconda_nightly_upload_url, but as it's practically an extra pip index, maybe dropping anaconda from the name and somehow adding pip instead would make sense. But I really don't have strong opinions on it, any naming works for me.

[skoudoro]

Thank all for the feedback.

It seems everyone is positif so I just created a PR(#47) to follow up on this.

[betatim]

Fine for me. Maybe we can use it to increase the number of people who are engaged with maintaining this action.

Though I think we should try and keep it reasonably focussed/tight in scope. Saying it out loud to keep those scope creep daemons under control ;)