[Actions] Globally resolvable action names

[silverwind]

Issue

Currently when using this on gitea.com:

- uses: actions/setup-python@v4

It will resolve to instance-specific URL https://gitea.com/actions/setup-python which I see very problematic because it makes action names ambigous across multiple gitea instances and github itself (where this will work).

Proposal

If the action URL is not absolute, assume a hardcoded https://github.com/ prefix, just like podman and docker assume a docker.io/ prefix on images not having a fully qualified name. This will ensure that action names are unambigously resolvable globally.

[delvh]

https://docs.gitea.com/administration/config-cheat-sheet#actions-actions DEFAULT_ACTIONS_URL?

[ChristopherHX]

I actually wish that DEFAULT_ACTIONS_URL (app.ini) is an array instead of a string.

With default value APP_URL (host your own actions via relative syntax), (https://gitea.com,
The last time I checked it was a place with mostly outdated copies of github),https://github.com

[silverwind]

The option is good but it must not be an option, it needs to be hardcoded to ensure it stays globally resolveable. So the proposal is to remove this configurability and hardcode it to https://github.com/.

If it can not be removed, at least make the default https://github.com/ so that users can destroy the global resolution on their instances themselves.

[delvh]

No.
Give me a reason for reopening.

[delvh]

That is not a good idea.

[delvh]

I actually wish that DEFAULT_ACTIONS_URL (app.ini) is an array instead of a string.
With default value APP_URL (host your own actions via relative syntax), (https://gitea.com,
The last time I checked it was a place with mostly outdated copies of github),https://github.com

okay, I can understand that.
Should we reopen this issue as that, or open a separate issue for it?

[ChristopherHX]

Should we reopen this issue as that, or open a separate issue for it?

Seems like I misunderstood the intention of this issue, my proposal should be a separate issue then.

However in both scenarios is actions/setup-python@v4 resolveable by default. So I thought that might be related.