Document that short-name can be used #8
No reviewers
Labels
No labels
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Status/Blocked
Status/Discuss
Type
Bug
Type
Feature
Type
Task
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ci/testing-farm!8
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "doc/short-name"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I'm not a fan of this as the full name makes this explicit and also makes it easier to find where the action is hosted.
Fair enough I am more used to the github actions and navigating with the short names. I'll add both formats for the user's preference
5502d87e161d88e45ad6Well, this works for GitHub because there is a single namespace for all orgs and repos. Here, if it's not specified, how do I figure out which one is used without running a job? It could the upstream Forgejo one or one from the local forge. There is no easy way to know as far as I know but I could be missing something.
@siosm wrote in #8 (comment):
It was changed recently, they all live here and are mirrored: https://forge.fedoraproject.org/actions/checkout
I guess it's a trade off.
If we use short names and I fork a repo here on another Forgejo instance then I have to fork all the actions as well, hoping that there are no conflicts with what's on my instance (otherwise I need to update the workflows).
If we use long names, then my fork will keep using the original ones and should work as is but if don't want to rely on the upstream forge then I need to update my workflows.
My preference still goes to being explicit by default but of course it's up to you.
Yeah, the confusion can come from both sides. It was confusing to me at first why the action did not pick up the short name and had to dig through how all of this works.
Migration wise it would be complicated regardless, there seem to be so many variables in how these runners are configured behind the scene (as we have seen this past month 🙂), I do not think even relying on absolute url will be 100% safe.
Anyway will leave it up to the user's preference.