GitHub Universe 2026: Call for Sessions Open Through May 1

GitHub Universe 2026 opens its Call for Sessions through May 1. Three formats, one goal: real engineering lessons delivered with personality. Here's what makes a Universe talk worth submitting.

GitHub Universe 2026: Call for Sessions Open Through May 1

TL;DR

  • GitHub Universe returns October 28-29 in San Francisco with Call for Sessions open until May 1
  • Three session formats: demo-style (including new Ship & Tell), thought leadership, and interactive workshops
  • Past sessions prove the best talks combine real engineering lessons with creative storytelling
  • You can submit your own proposal or nominate someone else to speak

The Big Picture

GitHub Universe isn't your typical developer conference. It's where Kubernetes security gets taught through D&D campaigns, Git optimization gets framed as a cat's nine lives, and CI/CD pipelines become fantasy quests complete with supply chain dragons. The 2026 edition lands October 28-29 at Fort Mason Center in San Francisco, and for the first time in a while, the organizers are making it clear: they want you on stage.

The Call for Sessions runs through May 1 at 11:59 p.m. PT. That's not a lot of runway, but it's enough if you've been building something worth sharing. GitHub is looking for talks that balance real technical substance with personality—sessions that teach developers something they can actually use, delivered in a way they'll actually remember.

This matters because Universe has become one of the few conferences where the community sessions rival the product announcements. While GitHub will undoubtedly showcase new features (recent launches like the Copilot SDK public preview suggest they're not slowing down), the event's reputation increasingly rests on its ability to surface creative, practical talks from builders who are shipping real products.

What Makes a Universe Talk Work

GitHub highlighted five standout sessions from recent years, and the pattern is obvious: the best talks take a genuinely useful technical concept and wrap it in a narrative that sticks.

Pillippa Pérez Pons turned frontend Git chaos—messy rebases, bloated monorepos, vanishing commits—into "Git's nine lives," with each life unlocking a lesser-known feature like sparse checkouts, partial clones, and reflog rescues. The cat metaphor wasn't just cute; it gave structure to what could've been a dry list of Git flags.

Matteo Bianchi and Alexandra Aldershaab went full fantasy RPG with "Breath of Copilot," casting CI/CD as a castle under siege and ancient scripts as lurking monsters. Underneath the theatrics, they delivered actionable patterns for securing GitHub Actions workflows while using Copilot to speed up automation. The storytelling made the security concepts easier to internalize.

Martin Woodward's "Dream it in the morning, build it in the afternoon" reframed velocity as a creative superpower rather than a productivity metric. He argued that the collapse of time between idea and shipped product changes what it means to be a developer—experimentation becomes the default mode, not a luxury. The session included a Furby. Somehow it worked.

The 2024 sessions leaned even harder into narrative. "Dungeons and deployments" turned Kubernetes security into a literal D&D campaign, complete with party members and villains. "Mission Copilot Autofix" played like a spy thriller, complete with a surprise ending that had people talking in the hallways.

The common thread: these weren't product pitches or abstract think pieces. They were grounded in real engineering problems, then elevated with creativity and a clear point of view. That's the bar for 2026.

What This Changes For Developers

GitHub is structuring submissions around three formats, and the choice matters more than you'd think.

Demo-style sessions include product demos and the new Ship & Tell format. Ship & Tell is explicitly aimed at startup founders and builders who want to share what they shipped, how they scaled it, what broke, and what worked. This is the format if you've been heads-down building and have war stories to share. It's less about polished slides and more about honest takeaways.

Thought leadership covers breakout sessions, panels, and fireside chats. These are longer-form, built for big ideas and perspectives with room for Q&A. If you're arguing for a shift in how developers think about a problem—like Martin Woodward's velocity-as-creativity angle—this is your lane.

Interactive learning means workshops and sandbox sessions. These are hands-on, participatory formats where attendees practice new skills in real time. If your talk requires people to actually run code or configure something, this is the right structure.

The format you choose signals what kind of experience you're offering. A Ship & Tell about scaling a side project into production is fundamentally different from a workshop teaching developers how to secure their Actions workflows. GitHub's submission guide breaks down the anatomy of each format, but the short version: match your content to the format that serves it best, not the one that sounds most prestigious.

For attendees, this structure means you can filter sessions by how you want to learn. Want to see what's possible? Hit the demos. Want to go deep on a concept? Workshops. Want to hear how other teams are thinking about AI-assisted development in the wake of tools like organization-wide Copilot customization? Thought leadership sessions.

How to Submit (Or Nominate Someone)

The submission process is straightforward: head to the Call for Sessions page, pick your format, and pitch your idea. GitHub's guide emphasizes clarity over cleverness—they want to know what you're teaching, why it matters, and what attendees will walk away with.

If you're not ready to speak but know someone who should, you can nominate them instead. This is worth doing. Some of the best conference talks come from people who didn't think they had anything to say until someone else pointed out that their "normal" work was actually worth sharing.

The deadline is tight: May 1 at 11:59 p.m. PT. That's less than two weeks from now if you're reading this in late April. Don't overthink it. The sessions that work aren't the ones with the most polished abstracts—they're the ones with a clear technical lesson and a speaker who cares enough to make it interesting.

The Bottom Line

Submit if you've shipped something real and learned something worth sharing. The best Universe talks aren't from people with the biggest titles or the most GitHub stars—they're from builders who can teach a specific skill while keeping an audience engaged. Skip it if you're planning to pitch a product without substance or deliver a generic "best practices" talk that could apply to anything.

The real opportunity here is that Universe has become one of the few conferences where creative delivery isn't just tolerated—it's expected. If you've been sitting on an idea for a talk but worried it's too weird or too niche, this is the venue. The risk isn't that your talk will be too unconventional. The risk is that it'll be too safe.

Source: GitHub Blog