[DevOps] Add Gitea Actions CI Workflow (fmt + clippy + test) #6
Reference in New Issue
Block a user
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?
Overview
Add automated CI that runs on every push and PR to keep the codebase clean and all tests green.
Steps
1. Create
.gitea/workflows/ci.ymlGitea Actions uses the same YAML syntax as GitHub Actions:
2. Pin MSRV in
Cargo.tomlChoose the oldest Rust version you intend to support; 1.78 is a reasonable baseline for
tokio1.x +axum0.7.3. Verify the Gitea Actions runner is registered
Check that the self-hosted runner for
git.aleshym.cois online and labelledubuntu-latest. If not, follow the Gitea Actions runner docs to register one on the homelab. The runner needscargo/rustupavailable or access to the Docker image that provides them.4. Add a CI status badge to
README.md5. Fix any pre-existing fmt/clippy warnings
Before merging, run
cargo fmt --allandcargo clippy --all-targets -- -D warningslocally and resolve all warnings so CI starts green.Acceptance Criteria
.gitea/workflows/ci.ymlexists and is syntactically validmainand on PRsmainbranch: fmt, clippy, testsCargo.tomlREADME.mdhas the CI badge