Javad Zeynal’s Post

🚀 GitHub just made code reviews a lot smarter with Stacked PRs (gh stack) If you’ve ever opened a massive PR and thought: Who is going to review this? you’re not alone. That’s exactly the problem GitHub is solving with stacked pull requests. 💡 Instead of one huge PR: You break your work into small, logical layers, each as its own PR, stacked on top of each other. 👉 Example: PR #1 → Auth logic PR #2 → API endpoints (depends on #1) PR #3 → Frontend (depends on #2) Each PR is: ✔ Easier to review ✔ Faster to merge ✔ Less prone to conflicts And the best part? 🔧 GitHub now supports this natively with: • A stack-aware UI (navigate layers easily) • Cascading rebases with one click • CLI support via `gh stack` • Ability to merge the entire stack together No more messy rebasing or waiting for one PR to merge before starting the next. 🔥 Why this matters: • Improves developer velocity • Makes code reviews actually meaningful • Reduces “PR fatigue” in teams This feels like a big step toward how modern teams should be shipping code. 🔗 gh stack: https://lnkd.in/dRvP8Cny #GitHub #SoftwareEngineering #DevWorkflow #CodeReview #Developers #Tech

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

Built a small CLI tool yesterday that solved a real annoyance. The problem: Writing git commit messages is tedious. VS Code GitHub Copilot helps, but it sometimes breaks when Husky pre-commit hooks run. And when I'm in Vim or Sublime, I don't want to open VS Code just for a commit message. The fix: A CLI tool that — → Reads your staged git diff → Sends it to Gemini 2.5 Flash → Generates a commit message → Lets you edit it before committing Now Husky works perfectly. Works in any editor. No more context switching. Code: https://lnkd.in/dH-d86Xu Sometimes the best tools are the ones you build for yourself. #OpenToWork #BuildInPublic #Git #AI #CLI #DevTools

Stop picking libraries blindly. Start vibe checking them. Every developer has been burned by a dependency that looked great on paper: → 50k GitHub stars → Slick README → "Used by thousands of companies" Then 6 months later: ❌ Last commit: 8 months ago ❌ 400+ open issues, 3 maintainers left ❌ Breaking changes with no migration guide ❌ Bus factor: 1 Stars don't tell you if a project is alive. Downloads don't tell you if it's healthy. That's why I built Vibe Check — a free tool that gives every GitHub repo a social profile with real signals: 🏥 Health Score — 6 metrics (activity, community, bus factor, issue health, docs quality, commit velocity) rolled into a letter grade from A+ to F 📡 Live Signals — recent GitHub events, npm/PyPI download trends, Hacker News mentions — all in real time 🎁 Repo Wrapped — Spotify Wrapped but for repos. Commits this year, longest streak, top contributor, busiest day 🔍 Dependency Scanner — paste your package.json or requirements.txt, get a vibe check on every dependency at once. Find the weak links before they break your build. 📊 Trending Leaderboard — GitHub Trending repos ranked by vibe score, not just stars How it works: Go to bubbling.dev/vibe Paste any GitHub URL Get the full picture in seconds No login. No paywall. Just signal. The next time someone asks "should we use this repo?" — don't guess. Vibe check it. 🔗 bubbling.dev/vibe What library burned you the hardest? Drop it in the comments and I'll vibe check it live. 👇 #OpenSource #GitHub #DeveloperTools #SoftwareEngineering #TechDebt #Dependencies #WebDevelopment #DevTools

GitHub adds Stacked PRs to speed complex code reviews A new feature to facilitate code reviews and prepare for an AI-driven surge in code changes. My PoV included in InfoWorld news today. https://lnkd.in/gF9kzM42

I found a bug in GitHub Copilot CLI's extension system last week. It was fixed in 2 days. Let that sink in. The issue: When creating extensions with hooks, my global hook flows were being overwritten — effectively breaking the governance layer I use to harden all my repositories. I filed the issue. Two days later, the GitHub team identified the root cause, pushed a fix, and it landed in production. But here's what's more interesting than the bug itself: GitHub didn't just patch the issue — they completely revamped the extensions ecosystem. In the span of a week, they shipped: → Custom slash commands in extensions via joinSession() → UI elicitation dialogs for structured user input → /extensions command for live enable/disable management → Multi-language SDK support (Node.js, Python, Go, .NET) → Session management that persists across restarts This signals a strategic shift. Extensions are no longer a power-user secret — they're becoming a first-class extensibility platform. For teams thinking about AI-assisted development at scale, this matters. The ability to create custom tools, intercept agent actions, inject context, and enforce governance through hook flows changes how you can operationalize AI coding assistants. The agentic era of development isn't coming. It's here. Full deep-dive in my latest video. #GitHubCopilot #DeveloperExperience #AITools

🚀 GitHub changed how I build. Earlier, I used to think of coding as just writing logic. Now I see it as building systems that evolve over time. GitHub is not just a code repository. 𝗜𝘁’𝘀 𝗮 𝘁𝗵𝗶𝗻𝗸𝗶𝗻𝗴 𝘁𝗼𝗼𝗹. Every commit = a decision Every branch = an experiment Every pull request = structured thinking Over time, I’ve built a simple workflow: 👉 𝗽𝘂𝗹𝗹 → 𝗯𝘂𝗶𝗹𝗱 → 𝘁𝗲𝘀𝘁 → 𝗰𝗼𝗺𝗺𝗶𝘁 → 𝗽𝘂𝘀𝗵 → 𝗶𝘁𝗲𝗿𝗮𝘁𝗲 Nothing fancy. Just consistent. And honestly, that consistency matters more than tools. Recently, I’ve been exploring AI-assisted development inside GitHub workflows. Using tools like: 𝗖𝗼𝗱𝗲𝘅-𝗯𝗮𝘀𝗲𝗱 𝗲𝘅𝘁𝗲𝗻𝘀𝗶𝗼𝗻𝘀 𝗔𝗜 𝗰𝗼𝗱𝗲 𝘀𝘂𝗴𝗴𝗲𝘀𝘁𝗶𝗼𝗻𝘀 𝗣𝗿𝗼𝗺𝗽𝘁-𝗱𝗿𝗶𝘃𝗲𝗻 𝗱𝗲𝗯𝘂𝗴𝗴𝗶𝗻𝗴 What I’ve realized: AI doesn’t replace GitHub. It makes GitHub more 𝗽𝗼𝘄𝗲𝗿𝗳𝘂𝗹. Because now: You don’t just write code 𝗬𝗼𝘂 𝗰𝗼-𝗯𝘂𝗶𝗹𝗱 𝘄𝗶𝘁𝗵 𝗰𝗼𝗻𝘁𝗲𝘅𝘁 For my current project (local AI content studio), GitHub is where everything comes together: 𝘣𝘢𝘤𝘬𝘦𝘯𝘥 𝘭𝘰𝘨𝘪𝘤 𝘌𝘭𝘦𝘤𝘵𝘳𝘰𝘯 𝘢𝘱𝘱 𝘣𝘶𝘪𝘭𝘥 𝘴𝘤𝘳𝘪𝘱𝘵𝘴 𝘦𝘹𝘱𝘦𝘳𝘪𝘮𝘦𝘯𝘵𝘴 All tracked. All versioned. All evolving. 💡 𝗠𝘆 𝘁𝗮𝗸𝗲𝗮𝘄𝗮𝘆: You don’t need complex setups. Start simple: learn basic git commands commit regularly use branches without fear experiment with AI tools That’s enough to level up. GitHub is not just where code lives. It’s where your 𝘁𝗵𝗶𝗻𝗸𝗶𝗻𝗴 𝗯𝗲𝗰𝗼𝗺𝗲𝘀 𝘃𝗶𝘀𝗶𝗯𝗹𝗲. If you’re building and figuring things out— we’re probably on the same path. #GitHub #LocalAI #VsCode

Day 22 of #30AppsIn30Days ⚡ I built a tool that writes my daily standup from my git commits. --- Every dev knows this moment. It's 9:58am. Standup in 2 minutes. You open Slack and completely blank on what you did yesterday. So you type: "Worked on some stuff, will continue today." The thing is — everything you need is already in your commits. GitPulse just reads them. --- Here's how it works: → Connect GitHub (read-only OAuth) → It fetches all your commits + PRs from yesterday → AI synthesizes them into a human-sounding update → Pick your tone: casual / professional / brief / detailed → One-click copy (or Slack-formatted) The whole thing takes about 10 seconds. --- A few things I learned building this: 1. GitHub's Events API is unreliable for this use case. It silently drops events and misses commits. The Commit Search API is the right tool — it queries the full index by author + date. 2. Free AI models get rate-limited constantly. Solution: a fallback chain of 5 models (Gemma 3 → Mistral → Qwen → Llama 3.3 → OpenRouter auto). If one fails, the next one picks up. Seamless. 3. Next.js Link + GitHub OAuth = CORS nightmare. OAuth needs a real browser redirect, not a client-side fetch. Switching from <Link> to <a> and returning a raw 302 fixed it instantly. --- Stack: Next.js 14 · GitHub OAuth · OpenRouter (free OSS models) · iron-session · Vercel Fully open source. Zero cost to run. → Website: https://lnkd.in/gXpThjHT → GitHub: https://lnkd.in/gQkZJsQ9 --- 22 apps shipped. 8 to go. What would you add to this? 👇 #BuildInPublic #NextJS #OpenSource #IndieHacker #SideProject #GitHub #AI #WebDev

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

GitHub Copilot is a pair programmer that suggests code snippets and full functions in real time inside your editor. It reads the surrounding code and comments to autocomplete patterns, draft unit tests, scaffold endpoints, and handle repetitive glue work. Best for developers who want to move faster and cut boilerplate without breaking flow. Use it to spike features, explore unfamiliar APIs, and standardize routine code. Guide it with clear function names and comments, review suggestions like any pull request, and keep security checks in place for critical paths. #GitHubCopilot #PairProgramming #DevTools