Allow 'DEFAULT_ACTIONS_URL' to Specify 'none' #11885

Open
opened 2025-11-02 09:50:54 -06:00 by GiteaMirror · 2 comments
Owner

Originally created by @P-N-L on GitHub (Oct 19, 2023).

Feature Description

Hello,

I just read through the following discussions/changes regarding DEFAULT_ACTIONS_URL.

My understanding is that this variable will default to github and can be set to self (though that is not recommended). The strongly recommended path forward seems to be to encourage use of fully-qualified action names (FQANs) and eliminate ambiguity, especially with a desire to push GitHub to support them.

This makes me wonder if adding a none or disabled option for DEFAULT_ACTIONS_URL would be useful. This setting would require that all action names be fully qualified, and avoid assuming anything in the first place. The default setting github could be retained for backwards compatibility on existing instances, but the docs could strongly recommend none and perhaps someday future releases of Gitea could remove the option altogether (an easier sell once GitHub supports FQANs). Ultimately, this would make it easy for entire instances (especially self-hosted ones) to enforce the better, less-ambiguous practice.

Thanks for your consideration,
Nick

Screenshots

No response

Originally created by @P-N-L on GitHub (Oct 19, 2023). ### Feature Description Hello, I just read through the following discussions/changes regarding `DEFAULT_ACTIONS_URL`. - https://github.com/go-gitea/gitea/issues/24789 - https://github.com/go-gitea/gitea/pull/25604 My understanding is that this variable will default to `github` and can be set to `self` (though that is not recommended). The strongly recommended path forward seems to be to encourage use of fully-qualified action names (FQANs) and eliminate ambiguity, especially with a desire to [push GitHub to support them](https://github.com/go-gitea/gitea/issues/24789#issuecomment-1554373485). This makes me wonder if adding a `none` or `disabled` option for `DEFAULT_ACTIONS_URL` would be useful. This setting would require that all action names be fully qualified, and avoid assuming anything in the first place. The default setting `github` could be retained for backwards compatibility on existing instances, but the docs could strongly recommend `none` and perhaps someday future releases of Gitea could remove the option altogether (an easier sell once GitHub supports FQANs). Ultimately, this would make it easy for entire instances (especially self-hosted ones) to enforce the better, less-ambiguous practice. Thanks for your consideration, Nick ### Screenshots _No response_
GiteaMirror added the type/proposal label 2025-11-02 09:50:54 -06:00
Author
Owner

@delvh commented on GitHub (Oct 19, 2023):

I mean… if you set it to self you basically achieve this already as most instances don't offer that many actions.
Of course, there are some you don't catch, but are those few really worth catching?

@delvh commented on GitHub (Oct 19, 2023): I mean… if you set it to `self` you basically achieve this already as most instances don't offer that many actions. Of course, there are some you don't catch, but are those few really worth catching?
Author
Owner

@silverwind commented on GitHub (Oct 19, 2023):

I think it makes sense to have a none when you want to strictly enforce FQAN. It would make the actions incompatible with GitHub until they support it, but if one is only concerned about running on Gitea, it will work and eliminate any amiguity in the action names.

@silverwind commented on GitHub (Oct 19, 2023): I think it makes sense to have a `none` when you want to strictly enforce FQAN. It would make the actions incompatible with GitHub until they support it, but if one is only concerned about running on Gitea, it will work and eliminate any amiguity in the action names.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#11885