#github-actions

6 posts tagged with #github-actions

Every article below is hand-written, technically reviewed, and focused on github-actions. Posts cover real-world architecture decisions, code-level implementation patterns, and trade-offs you'll only discover after shipping production systems.

a white dice with a black github logo on it Developer Tools

LLM Knowledge Base GitHub Template [2026]: Starter Kit Repo

Ship a forkable LLM knowledge base starter kit: a clean repo layout, ingestion scripts, GitHub Actions freshness checks, agent-readable templates, and retrieval evals that don’t rot.

a key chain with a key Developer Tools

Rust Reproducible Builds + SBOM + Signed Artifacts [2026]

A 2026-ready Rust release pipeline: pin toolchains, make builds reproducible, gate deps with cargo-vet, generate SBOM + SLSA provenance, and sign everything with keyless cosign.

a white dice with a black github logo on it Developer Tools

How to Build a Rust Version Bump Tool [2026 Tutorial]

Build a CI-safe Rust release toolchain: semver bump rules, workspace updates, changelog generation, annotated/signed git tags, and reproducible benchmarks.

Computer screen displaying code and terminal prompts Developer Tools

How to Set Up gitleaks + pre-commit + CI [2026]

A terminal-first, defense-in-depth secrets workflow for 2026: staged-only hooks, CI full-history scans, baselines for legacy repos, and sane allowlists.

Computer screen displaying code and terminal prompts Developer Tools

AI Code Review in Your CI/CD Pipeline: 2026 Setup

Every vendor shipped a 2026 'best tools' listicle. None shipped the YAML. Here's a complete, copy-pasteable GitHub Actions config that wires AI code review into your pipeline — triggers, secrets, cost caps, and a real merge gate.

GitHub Actions vs CircleCI 2026: Which CI/CD Pipeline Wins? Developer Tools

GitHub Actions vs CircleCI 2026: Which CI/CD Pipeline Wins?

I'd pick GitHub Actions for solo devs and GitHub-native teams who want zero-friction setup; I'd pick CircleCI for performance-obsessed teams who need faster parallelism and fine-grained resource control. The split isn't about features — it's about where your bottleneck actually lives.

Keep exploring

Close to this topic, not on this page.