explaingit

github/roadmap

★ 8,730Audience · pm founderComplexity · 1/5Setup · easy

TLDR

GitHub's official public product roadmap, listing planned features as issues with labels for release phase, product area, and which subscription tier or platform each item applies to.

Mindmap

mindmap
  root((GitHub Roadmap))
    What it is
      Public feature announcements
      Issue-based board
      No code included
    Release Phases
      Preview limited access
      GA production ready
      In design or exploring
    Organization
      Quarterly board view
      Product area labels
      Platform labels
    Interaction
      Read-only issues
      Linked feedback discussions
    Audience
      GitHub users
      Product planners
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Track which GitHub features are in preview, generally available, or still in design so you can plan your team's workflows accordingly.

USE CASE 2

Check the quarterly project board to see what GitHub improvements are expected in the near term versus further out.

USE CASE 3

Provide feedback on planned features by participating in the linked discussions attached to roadmap items.

USE CASE 4

Monitor whether a specific upcoming GitHub feature will be available on GitHub.com, GitHub Enterprise Server, or both.

Getting it running

Difficulty · easy Time to first run · 5min
No license information is mentioned in the explanation.

In plain English

This repository is GitHub's public product roadmap, a place where GitHub communicates what features and improvements it is planning to build, what stage each item is in, and roughly when it expects to release them. It is not a code project. It is a collection of issues that serve as a structured announcement board. Each roadmap item is an issue with labels describing its release phase, the product area it belongs to, the specific feature or product involved, which GitHub plans or subscription tiers it applies to, and whether it will be available on the cloud version of GitHub, the self-hosted server version, or both. Release phases have defined meanings. Preview means the feature is available in some form but without formal support guarantees. GA, short for generally available, means it is ready for production use with support. Items marked in design or exploring are earlier stage, meaning GitHub has decided to work on them or is gathering feedback, but no release date is set yet. The roadmap is organized by quarter on a project board, so you can see roughly which features are expected in the near term versus further out. GitHub notes that dates are subject to change, particularly for items further out on the timeline, and the roadmap does not represent a binding commitment to ship anything by a specific date. The repository exists to give GitHub users and customers visibility into what is coming and a place to provide feedback through linked discussions. Existing issues in the repository are read-only, so the primary interaction is reading the roadmap and participating in the separate feedback discussions rather than commenting directly on issues.

Copy-paste prompts

Prompt 1
Look at the github/roadmap repository and summarize which features are currently in preview and expected to reach GA this quarter.
Prompt 2
I'm evaluating GitHub Enterprise Server versus GitHub Cloud for my team. What features on the GitHub roadmap are Server-only or Cloud-only?
Prompt 3
What GitHub Actions improvements are listed on the github/roadmap that would affect CI/CD pipelines in the next 6 months?
Prompt 4
How do I find and participate in the feedback discussion for a specific planned feature on the github/roadmap repository?
Open on GitHub → Explain another repo

← github on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.