Migrate CI to 4-job pipeline with SHA-pinned actions #1
Reference in New Issue
Block a user
Delete Branch "feat/gitea-actions-v2"
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?
Summary
Migrate CI pipeline to a standardized 4-job workflow:
tests/test.shChanges
.gitea/workflows/docker-build.yaml: New 4-job lint→build→test→push pipeline, all actions pinned to commit SHAstests/test.sh: Added smoke test (unrar usage output)Dockerfile: Added# hadolint ignore=DL3018beforeRUN apk addNotes
jcabillot/unrar-arm64:lateston Docker HubChristopherHX/gitea-*actions for artifact upload/download (Gitea-compatible)View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.