Add Production-Grade CI Pipeline: fmt, clippy -D warnings, Tests with Live Postgres/Redis, sqlx Drift Check, Docker Build, Dependency Audit

[Christopherdominic]

Summary

This repository has no CI whatsoever — .github/workflows/ does not exist. A 53-module Axum/SQLx service with Postgres, Redis, Docker, Helm, and k8s manifests is merged entirely on trust: no fmt, no clippy, no tests, no build verification runs on any PR.

Task

Implement a production-grade GitHub Actions pipeline that runs on every PR and push to main:

1. ci.yml with parallel jobs:
   • fmt — cargo fmt --all --check
   • clippy — cargo clippy --all-targets --all-features -- -D warnings
   • test — cargo test --all-features with Postgres and Redis service containers, running the SQL migrations in migrations/ before the suite; integration tests in tests/ must actually execute, not be skipped
   • sqlx — offline query metadata check (cargo sqlx prepare --check) so schema drift breaks the build, wiring up .sqlx/ metadata if not present
   • docker — docker build of the production Dockerfile (build-only, no push), with layer caching
2. audit.yml — cargo audit (or cargo deny check advisories licenses bans) on PRs and on a weekly schedule.
3. Shared Rust toolchain pinning via rust-toolchain.toml, Swatinem/rust-cache for incremental caching, and a concurrency group cancelling superseded runs.
4. Total wall-clock under 20 minutes on a warm cache; document the cache strategy in the workflow comments.
5. Status badges in README.md.

Acceptance criteria

• All five CI jobs green on your own PR — the pipeline must prove itself
• Integration tests demonstrably run against real Postgres/Redis services (visible in job logs)
• cargo sqlx prepare --check fails the build on schema drift (demonstrate once in a draft commit if possible)
• Clippy passes with -D warnings — fix any warnings this surfaces rather than allow-listing them
• Weekly dependency audit scheduled

PR requirements (mandatory)

• ✅ Your PR must pass all checks — PRs with failing or skipped checks will not be merged.
• 📸 You must attach a screenshot in the PR description demonstrating the result (for this issue: the green Actions run summary showing every job passing).
• 🔗 You must link this issue number in your PR description (e.g. Closes #<issue-number>). PRs without a linked issue will not be reviewed.

[Markodiba]

Why I'm a good fit for this is because, Experience setting up CI/CD pipelines for backend services in production environments (Azure DevOps pipelines against OpenShift/Kubernetes deployments), so the shape of this problem — parallel jobs, service containers, caching, fast feedback — is familiar even outside the Rust-specific tooling.
Background working across Postgres-backed services means the sqlx prepare --check schema-drift requirement is a pattern I understand the value of, not just a checkbox: catching drift at CI time instead of at deploy time is exactly the kind of gap worth closing here.
Comfortable treating "the pipeline must prove itself" literally — I'll make sure the PR that adds the CI is the first real exercise of it, including demonstrating the sqlx drift-catch and clippy warning fixes rather than working around them.

[grantfox-oss]

🦊 GrantFox — @Markodiba has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #337)
2. Your PR will be reviewed by the Bonizozo maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign | FWC26 campaign!

@Markodiba's PR #356 was approved and merged by @Christopherdominic.

🏆 @Markodiba: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (306 total points). Track your full progress on GrantFox.

👏 Great work, @Markodiba! Keep contributing to Bonizozo.