Avoid Blindly Picking Libraries with Vibe Check

GitHub just officially entered the stacked PRs game - and it's a big deal. 🎉 If you've never heard of stacked PRs, here's the idea: instead of one massive pull request that's painful to review, you break your changes into a chain of smaller, focused PRs that build on each other. Each layer is independently reviewable. CI runs on all of them. Branch protection rules apply across the whole stack. And when you're ready, you can merge the entire thing in one click. GitHub's new native implementation includes: - A visual stack map right in the PR UI - The gh stack CLI for managing branches, rebases, and pushes - Merge queue support that's stack-aware - Auto-rebase of remaining PRs after a merge No more rebase hell. No more wondering if CI is passing for mid-stack PRs. No more losing review context on a 2,000-line diff. The concept isn't new. Facebook built Phabricator around stacked diffs back in 2011. Tools like Graphite have offered this on GitHub for years. But having it natively supported changes things. The bottleneck in modern development is no longer writing code - it's reviewing it. Currently in private preview. Worth joining the waitlist if you work on large codebases or fast-moving teams. #GitHub #SoftwareEngineering #DevTools #CodeReview #DeveloperExperience

🚀 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

> GitHub stopped updating its own status page due to terrible availability ... 90.1% uptime - This means ... issues/degradations for 2.5 hours daily ... > GitHub struggles to keep up with the increase in load from AI agents generating more code and pull requests ... Claude Code bot contributions growth in the past 3 months has been enormous ... Stream of outages ... https://lnkd.in/eYHzasTh

I want to share something important that happened to me especially for students and developers using GitHub Student Developer Pack. Like many of you, I got access to premium tools (Claude, GPT, etc.) through the pack. Instead of using them as intended, I tried to get creative I installed GitHub Copilot CLI, used the models, and set up a local server to act as a proxy for Claude Code. I don’t hesitate to spend on hardware because I know I’ll use it or anyone in my team can, but when it comes to software, I often look for workarounds instead of paying. I tend to rely on proxies or alternative routes to access premium tools and latest models rather than using them the intended way. For about 8 days, everything seemed fine. Then reality hit. I received an email from GitHub: 👉 My access was revoked 👉 My account was suspended 👉 Multiple repositories were taken down and placed under review That’s when I realized what seemed like a “smart workaround” was actually a violation of their terms. Some context: - I had applied for the Student Pack multiple times before (faced rejections too) - Finally got approved recently - Within days of using it this way, I lost access entirely 💡 Lesson learned (the hard way): Just because you can do something technically doesn’t mean you’re allowed to do it. These tools come with usage policies, and bypassing intended usage (like creating proxies or reselling access) can lead to serious consequences including account suspension. I’ve raised a support ticket with GitHub. Let’s see how it goes. Sharing this so others don’t make the same mistake. #github #StudentDeveloperPack #Copilot #AI #Developers #LearningTheHardWay

You assign a GitHub issue before lunch. By the time you're back — there's a pull request waiting. That's the GitHub Copilot Coding Agent. GitHub Copilot has evolved far beyond autocomplete. The Coding Agent now works asynchronously in the background — fixing bugs, writing tests, refactoring code — and hands you a ready-to-review PR when it's done. Here's what just shipped: 🎛️ Model picker — Choose Claude Opus, Claude Sonnet, GPT-Codex-Max, or let Auto decide. Pick the right model for the complexity of each task. 🔍 Self-review — The agent reviews its own diff before tagging you. By the time you're looking at it, someone already went through it once. 🔒 Built-in security — Code scanning, secret scanning & dependency vulnerability checks — all before the PR opens. Free with Copilot coding agent. 🔌 MCP servers — Plug in external tools, databases, and context via Model Context Protocol. Your agent now has eyes beyond the repo. The agent boots a VM, clones your repo, RAG-indexes your codebase, and starts coding. You track every step in session logs. Your branch protections, CI/CD approvals, and security posture? Untouched. Think of it as having a junior dev who never sleeps, never skips tests, and always opens a clean PR. What low-to-medium complexity tasks would you hand off to an agent first? Drop a comment 👇 #GitHubCopilot #AI #CodingAgent #SoftwareEngineering #DevTools #AgenticAI #GitHub

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

Hot take: GitHub is missing its most obvious feature. Steam has had user reviews for over a decade. You can see what real players think before you download a game. But open source? You're on your own. You find a repo with 2k stars. Looks promising. Then you spend half a day discovering: → The docs are outdated → The maintainer ghosted 8 months ago → There's a subtle bug that 47 issues reference but nobody's fixed Stars don't tell you any of this. Stars are bookmarks disguised as endorsements. What if GitHub had Steam-style reviews? Think about it: → "Great library, but expect breaking changes every minor release" ⭐⭐⭐ → "Rock solid. Running this in production for 3 years, zero issues" ⭐⭐⭐⭐⭐ → "Amazing concept, mass grave of PRs. Fork it." ⭐⭐ And here's the thing Steam gets really right: every review is timestamped. You can instantly tell if the glowing 5-star praise is from 2019 or last week. A repo that was great two years ago might be abandonware today. Dates turn reviews from static noise into a living timeline. Real context from real users. Not just a star count that could mean "I'll read this later" or "this saved my company." Open source deserves better signal than a single binary button. Who's building this? 🚀 Learn how to build Open Source repositories and more only on Quro AI → https://lnkd.in/gaR45DJf #OpenSource #GitHub #SoftwareDevelopment #DevCommunity #TechInnovation

🚀 I built a Chrome Extension that automates something I was doing manually every single day. Introducing LeetPush — a tool that pushes your LeetCode solutions directly to GitHub with a single click. Here's the problem I kept running into: → Solve a problem on LeetCode ✅ → Copy the code manually 😐 → Open GitHub, create a file, name it, write a commit message 😩 → Repeat. Every. Day. So I built the fix myself. What LeetPush does: ✦ One-click push — straight from LeetCode to your GitHub repo ✦ Auto-generates commit messages like "Add: 1. Two Sum [Easy]" ✦ Organizes solutions into folders by topic or difficulty ✦ Detects duplicates — overwrite or save as v2 ✦ Undo your last commit right from the popup ✦ Supports multiple repos (e.g. leetcode-easy vs leetcode-hard) ✦ Dark/light mode, 100% local storage — no third-party servers Your GitHub profile becomes your DSA portfolio — automatically. Watch the demo 👇🏼 (screen recording below) —————————————————— 🧪 Want to try it right now? Here's how: 1️⃣ Clone or download the repo from GitHub --> https://lnkd.in/gWXMeqHJ 2️⃣ Go to chrome://extensions → enable Developer Mode → Load Unpacked → select the folder 3️⃣ Create a GitHub PAT: Settings → Developer Settings → Tokens (classic) → check the "repo" scope 4️⃣ Open LeetPush, paste your token + repo name in Settings 5️⃣ Solve any LeetCode problem → click Push → done ✅ Takes less than 3 minutes to set up. —————————————————— Drop a ⭐ or comment if you'd find this useful — feedback means a lot at this stage. Chrome Web Store listing coming soon. Repo link 👇 #buildinpublic #chromeextension #leetcode #github #dsa #opensource #softwareengineering #codinginterview #sideproject #developer

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