j3ffyang·Oct 14Keeping secrets out of GitSecrets, credentials, and keys belong on the local disk and nowhere else — not in a commit, not in a push, not in a branch, not in a pull…
Dawid Kowalski·Aug 9Bandit OverTheWire Writeup — Level 31 → Level 32Up until now, we’ve been digital detectives — searching through history, branches, and tags. In this level, the game changes. We aren’t…
Pranshi Verma·Jul 23.gitignore, README Files & GitHub Issues — Making Your Projects Look ProfessionalIn Day 1, we pushed code. In Day 2, we learned to branch and merge like a real team. Today we polish everything — keeping junk files out of…
Tarek Najem·Jun 3Jeninnet.FileQueryBuilding a Deterministic File Query Engine for .NET Technical Whitepaper
Constanza Diaz·Jun 1Security by Design: Keeping API Tokens Out of Git with a 3-Layer SetupWhen you build a product whose entire reason to exist is safety, security can’t be something you bolt on later. It has to be a default.
Tharindu Yehan·Apr 16The GitHub Survival Guide: Stop Pushing Your Secrets & BloatWe’ve all been there. You finish a feature, hit that big “Commit” button in VS Code, and boom your private API keys are live on GitHub for…
Nkulumdubeki·Mar 28How to Handle Sensitive Data Securely in TerraformDay 13 of the 30-day IaC challenge — three secret leak paths, AWS Secrets Manager integration, sensitive value handling, and state file…
InThe OwlbySiladittya Manna·Jan 29How to Remove Large Files from Git History(and Why git rm --cached Seems to Work)
