🚀 Just shipped Auto-Deploy on Nexus — push to GitHub, go live automatically. I've been building Nexus, a full-stack deployment platform (think a self-hosted Vercel), and today I shipped a feature that completes the CI/CD loop: ⚡ GitHub Auto-Deploy via Webhooks Here's what it does: → Connect your GitHub repo to a Nexus project → Enable Auto-Deploy with one toggle → Get a unique webhook URL + HMAC-SHA256 secret → Paste it into GitHub's webhook settings → From that moment, every push to your tracked branch triggers an automatic deployment — no manual clicking required And the engineering behind it wasn't trivial: 🔐 Secure by design — Every incoming webhook is verified using HMAC-SHA256 signature validation (timing-safe compare). Invalid signatures are rejected before any logic runs. 🧱 Middleware ordering matters — The biggest gotcha was that Express's express.json() consumes the raw body stream, making HMAC verification impossible. The fix was registering the webhook route with express.raw() before the JSON middleware — the same pattern used for Stripe/Razorpay webhooks. 🛡️ Multiple safety layers: Branch matching (only deploy on the right branch) Repo URL identity check (no cross-repo spoofing) Build quota enforcement before triggering Branch deletion events are gracefully skipped 📦 Full stack: TypeScript, Node.js, Express, MongoDB, React — deployed with its own infrastructure. If you're building something and tired of manually clicking "redeploy" every time you push — this is the workflow you want. 👉 I'm looking for early testers: If you want to try Nexus and ship your frontend projects with one push, here's the link https://madhavkumar.tech #buildinpublic #webdev #devtools #nodejs #typescript #cicd #opensource #deployment #javascript #react #github

GitHub engineering team tackled massive performance issues in the new React-based “Files changed” tab for huge pull requests, where things like 1GB JS heaps and laggy interactions were killing the vibe. By simplifying diff line components, ditching unnecessary DOM nodes and event handlers, adding virtualization for mega PRs, and optimizing state/rendering, they slashed memory by 50%, DOM nodes by 10-74%, and made interactions way snappier. https://lnkd.in/gC_Mweez

Hey devs 👋 I built a small desktop app for one annoying part of shipping code: writing commit messages that sound like you were done with life halfway through. It’s called **GitRoast**. You know the moment: you finish coding you run `git add .` and then suddenly your commit message is: `fix stuff` GitRoast reads your **staged changes** and gives you **one clean commit message** worth copying into your normal workflow. That’s it. I didn’t want this to become: * a full Git client * an auto-commit tool * a file editor * another workflow to learn The goal was simple: keep Git exactly how it is, just make commit writing faster and less boring. How it works: 1. Open your repo 2. Stage what matters 3. Click **Generate** 4. Copy the commit 5. Keep shipping 🚀 A few things I cared about: * repo inspection stays local * only staged Git data is sent when you click **Generate** * no full repo upload * no file editing * no auto-commits It’s built for devs who already like Git the way it is — they just want less friction and fewer commits like: `update` `fix` `stuff` `final_final_v2` If that sounds familiar, you might enjoy this 😄 👉 Check out the GitHub repo: (https://lnkd.in/ggQRQvp8) 💛 If you’d like to support GitRoast and future releases: (https://lnkd.in/gfK_BTvW) My commits still aren’t perfect. They’re just less emotionally exhausted now. #developers #git #productivity #desktopapp #buildinpublic #tauri #javascript #frontend #backend #ai #git #commit #fullstack #forfun

Most portfolio projects could be built in a weekend. I wanted to build something that couldn't. So I reverse-engineered how GitHub works and built RepoDoc — a full-stack version control platform with a custom Git-like CLI, completely from scratch. Here's what it actually does: 🗂️ Repos → Full CRUD, in-browser file editing, commit history, S3-backed storage 👤 Users → Profile management, image uploads, JWT auth 🐛 Issues → Create, update, close, delete per repository ⭐ Social → Star / Unstar repos 💻 Custom CLI: init → spins up a local .repoGit directory add → stages a file commit → commits everything staged push → ships files to AWS S3 pull → pulls latest from S3 revert → rolls back to any commit by ID The CLI and integrating AWS with it alone took longer than most of my previous projects combined. Because when you build the tool instead of just using it, you finally understand it. The real takeaway wasn't the tech stack. It was finally understanding why the tools we use every day are designed the way they are. You don't get that from tutorials. You get it from breaking things and fixing them yourself. 🎥 Short walkthrough below. Drop your thoughts! 🔗 Live link in the comments. If you've ever built dev tooling from scratch, what broke first? #softwareengineering #buildinpublic #fullstackdevelopment #reactjs #nodejs #javascript #aws

🚀 I built a tool to analyze what your GitHub profile actually says about you. As developers, our GitHub profile is often our most authentic portfolio — but we rarely stop to evaluate what it communicates. That’s what inspired me to build this GitHub Profile Analyzer. 🔍 What it does: → Search any GitHub username instantly → View repositories, profile stats & activity → Analyze top programming languages → Real-time data via GitHub REST API → Clean, responsive UI with proper error handling 💡 Why I built this: Most developers don’t realize what their GitHub profile communicates — this tool makes that visible instantly. 🛠️ Built with: React.js • Vite • Tailwind CSS • GitHub REST API • JavaScript ⚡ Challenges I solved: → Efficient API handling with Promise.all → Reusable and scalable API structure → User-friendly error handling → Input validation to prevent invalid requests Building this taught me that writing code is just one part — structuring it well and handling edge cases is what makes a real difference. 👉 Try searching your own GitHub username and see what stands out 👀 👉 Live Demo: https://lnkd.in/dhUYq6h3 💻 GitHub Repo: https://lnkd.in/dcgUXPFR What feature would you like to see added next? Drop it in the comments 👇 #React #JavaScript #Vite #TailwindCSS #GitHub #OpenSource #BuildInPublic #WebDevelopment #DevTools #FrontendDevelopment

🚀 6 Free GitHub Repos That Can Save You $100+/Month on Claude Code If you're deep in Claude for daily coding and your token bill is creeping up, this one's for you. I came across this brilliant hand-drawn breakdown (image above) and had to share it. These 6 open-source tools are quietly helping developers cut costs while getting sharper, faster, and more useful outputs. Here’s the quick hit list: 1. vercel-labs/agent-browser Replaces Claude in Chrome. Uses the accessibility tree instead of screenshots or messy HTML. Clean context, zero noise. 2. rtk-ai/rtk 60-90% faster on common commands (npm run, git commit, pnpm test, etc.). Real-world savings of 20-30% in actual workflows. 3. juliusbrussee/caveman The “terse-output” skill we all needed. Drops the fluff and filler. Responses become direct: “use map(), not filter(). Return acc.” 4. tirth8205/code-review-graph Up to 49× fewer tokens on daily coding tasks via AST mapping. One of the biggest efficiency wins on the list. 5. Gronsten/claude-usage-monitor Real-time 5-hour usage window + live active-session token tracking. Know exactly where you stand before you hit the cap. 6. phuryn/claude-usage Historical breakdowns by session, day, and week. Beautiful charts showing exactly where your tokens (and money) went — and what to fix. The real magic? Stack them. Use what you need. Save money. Ship more. Compounding wins. These are all free, actively maintained, and built by the community. If you’re serious about getting more signal and less spend from Claude, go star them now. Which one are you trying first? Or drop your own favorite Claude optimization tool in the comments 👇 Let’s help each other build faster and cheaper. #ClaudeAI #Anthropic #AIforDevelopers #GitHub #DeveloperTools #TokenOptimization #Productivity #OpenSource #SaveMoney

If you've checked HackerNews or Lobsters this morning you'll see that GitHub has finally launched a stacked pull request in private preview. The long-awaited coding workflow is wait-list only at the moment, but that hasn't stopped devs and users from weighing in. The full story is on The Stack now. https://lnkd.in/e6m8qPP8

🚀 Day 93 of #1000DaysOfCoding Today was less about coding… and more about becoming a real developer. I finally moved my full-stack project from local to GitHub — sounds simple, but the journey was full of real-world challenges: 💥 Faced Git errors like large file limits 💥 Accidentally pushed node_modules (never again 😅) 💥 Learned why .gitignore is not optional 💥 Understood how Git actually tracks history (not just files) 💥 Fixed branch & remote issues like a pro And the best part? ✅ Clean repo structure ✅ Proper version control setup ✅ Ready for deployment 🚀 This wasn’t just “uploading code” — It was understanding how developers actually work in production. 💡 Small lesson: If your code works locally but you can’t version or deploy it — you’re not done yet. Next step: 👉 Deploying this project live (Frontend + Backend + DB) Let’s see how it goes 🔥 #1000DaysOfCoding #Day93 #Git #GitHub #FullStackDevelopment #SpringBoot #ReactJS #MongoDB #LearningInPublic #DeveloperJourney

Hey folks 👋 after my last post i.e (building a design system on Claude) a consistent concern was the friction of maintaining a Claude skill (design system) across different workspaces updating it, re-uploading it, sending it over Slack again and again. It just wasn’t sustainable for a real team setup. So… to solve this problem👇 We moved everything to GitHub cloud-based platform 😼 Now upload the entire design system repo foundations, tokens, rules and that becomes the single source of truth. I connect that repo directly to Claude Code using GitHub CLI, and that’s it. Now when anyone on the team pulls it into Claude Code, they’re all working from the same live version. Update the repo → everyone gets the update. ☕ No manual sharing. No version confusion. No drift. If you want to try it, here’s the quick setup to connect github with claude code 1️⃣ Open Terminal Press Cmd + Space → type Terminal → hit Enter 2️⃣ Install Homebrew Paste this command and press Enter: /bin/bash -c "$(curl -fsSL https://lnkd.in/dedBGCGW)" It will ask for your Mac password → type it and press Enter (you won’t see the characters while typing that’s normal) Wait ~5 minutes for it to install Type "done" when Homebrew setup finish 3️⃣ Install GitHub CLI brew install gh 4️⃣ Log into GitHub gh auth login Choose: GitHub.com → HTTPS → Yes → Login with a web browser Then: You’ll get a one-time code (e.g. ABCD-1234) Copy it, press Enter → your browser will open Paste the code → click Authorize → done ✅ Once it’s connected, you can call the repo directly inside Claude Code. The design system stops being “a file someone owns” and becomes a shared, versioned, cloud-based system the whole team designers, devs, PMs can rely on. That’s really the collaboration piece that was missing. 🔁 Still early days, but this is the closest we’ve come to something that actually works at scale. P.S. There is a bit of a learning curve (especially if Terminal isn’t your thing), but once it’s set up, you’re basically done. #claude #ai #github #claudecode #terminal #productdesigners #designsystem