Practical guides to Git, CI/CD, Ollama, and Azure
Use git reset to move your branch back, git revert to undo a commit with a new commit, and git restore to fix files without touching history. The git reset vs revert choice comes down to one question: has anyone… Read moreGit Reset vs Revert vs Restore: Which to Use
I ran ansible-lint against a four-task playbook that looked fine at a glance. It reported 14 violations and exited with code 2. Setting up that same check as an Ansible Lint GitHub Actions workflow takes about ten lines of YAML,… Read moreAnsible Lint GitHub Actions: Fail PRs on Bad Playbooks
Grafana Tempo 3.1 shipped on 2026-09-30 with a feature that matters the moment something goes wrong, not when everything’s fine: redaction by query. Before this release, scrubbing a leaked secret out of your traces meant enumerating trace IDs one at… Read moreGrafana Tempo 3.1: Query-Based Trace Redaction Explained
A GitHub Actions workflow not triggering almost never means GitHub is broken. It means one of about a dozen rules quietly filtered your event out: the workflow file is on the wrong branch, a filter didn’t match, the commit was… Read moreGitHub Actions Workflow Not Triggering? Every Cause and Fix
Git 3.0 changes the default hash function, the default reference storage format, the default branch name, and the build toolchain required to compile Git at all. None of this is speculation. It comes straight from git-scm.com’s own BreakingChanges documentation. That’s… Read moreGit 3.0: What Actually Breaks (SHA-256, Rust, More)
In March 2025, a single compromised GitHub Action leaked secrets from more than 23,000 repositories. In the same window, security researchers used a well-known workflow-trigger mistake to reach remote code execution in CI pipelines at Microsoft, Google, and Nvidia. These… Read moreGitHub Actions Incidents: What Actually Breaks in Production
If you run GitHub Actions self-hosted runners, the enforcement clock isn’t approaching — it’s already running. GitHub’s minimum-version enforcement blocks registration below version 2.329.0. It’s been fully in effect for GitHub Enterprise Cloud with data residency since July 31, 2026,… Read moreGitHub Actions Self-Hosted Runners: Fix Before Sept 25
Git 2.55 landed on June 29, 2026, and the headline change isn’t a new command — it’s a build requirement. Starting with this release, building Git from source requires a Rust toolchain unless you explicitly opt out. Alongside that, Git… Read moreGit 2.55: History Fixup, Rust by Default, Safer Checkouts
If you run Kubernetes in production, you have probably heard the word GitOps. It comes up in job descriptions, tool documentation, and architecture discussions. But a lot of explanations are vague or overcomplicated. This post explains GitOps clearly — what… Read moreGitOps Explained — What It Is and Why It Matters
Ingress NGINX has been one of the most widely used ingress controllers in Kubernetes. For many teams, it became the default solution for exposing applications securely. However, the Kubernetes community has officially announced that Ingress NGINX is being retired. Because… Read moreIngress NGINX Retirement: Migration Guide & Timeline