April 26, 2026
Modal meltdown at GitHub
GitHub unwanted UX change: issue links now open in a popup
Devs fume as simple links trigger surprise pop-ups, begging for a revert and an off switch
TLDR: GitHub changed issue links to open in pop-up overlays, and users say it hurts productivity and wasn’t announced. The community’s roasting the move, demanding a revert or opt-out while venting about buggy big-tech UX and “AI bloatware,” arguing they need stability over surprise experiments.
GitHub quietly flipped a switch and boom—clicking an issue link now opens in a pop-up overlay instead of a normal page. In a fiery community thread, users say the change “completely breaks the experience,” with no mention in the changelog and no way to turn it off. The vibe? Modal-gate. The ask? Give us a revert or at least an opt-out.
Commenters came in hot. One begged someone to “tap” GitHub and reverse it. Another dropped the line that’s fast becoming the meme of the moment: “Links should be links.” Others widened the blast radius: stop chasing shiny features and fix reliability. One user called the trend “AI bloatware,” saying GitHub will lose that race anyway. And the pile-on didn’t stop at GitHub—someone dragged LinkedIn’s ad tools and Google’s ad UX for being clunky, turning it into a roast of Big Tech’s basic buttons.
There’s no real counter-fandom here—just a chorus of “why?” and “who asked for this?” The modal feels like Linkception to many: you click a link and end up playing pop-up whack-a-mole. For developers who live in issues all day, that extra layer slows them down. Until GitHub responds, the prevailing take is simple: stop the surprise experiments, ship stability, and let GitHub Issues be boring—in the best way.
Key Points
- •A GitHub Community post reports issue links within issues opening in a popup overlay instead of navigating to the issue page.
- •The behavior is observed only in some repositories, indicating inconsistent application.
- •The author checked GitHub’s changelog and product roadmap and found no mention of this change.
- •The post asks if the behavior is a gradual rollout and whether it can be disabled or configured.
- •The author states the change disrupts user experience and reduces productivity.