Is the {upload,download}-artifact@v4 fork still necessary? #159
Labels
No labels
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
Dependencies
No dependencies set.
Reference: forgejo/runner#159
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
forked version of the action that claims to not be GHES are advertised in the comment of the mirror at:
and they are made available at:
To verify it is still needed, modify https://code.forgejo.org/forgejo/end-to-end/src/branch/main/actions/example-artifacts-v4/.forgejo/workflows to use the mirror instead of the fork:
If it fails, it is still needed. Otherwise it can be removed.
Is the {upload,download}-artifacts@v4 fork still necessary?to Is the {upload,download}-artifact@v4 fork still necessary?