Action needed by GitHub Connect customers using GHES 3.1 and older to adopt new authentication token format updates
Upgrade to GHES 3.2 or newer by June 3rd to continue using GitHub Connect.
The public roadmap is designed to give your team more information about what features and functionality you can expect from GitHub over the coming quarters.
In the last year, we’ve released more than 200 new features, including:
We’re also building many of our features iteratively with the open source community, including the recent GitHub Discussions beta. As customers have gotten used to us shipping new things, we’ve also heard you clearly tell us that you’d like more visibility into what we’re working on, what we’re going to be shipping, and when.
Today, we’re excited to announce the GitHub public roadmap. The public roadmap is designed to give your team more information about what features and functionality you can expect from GitHub over the coming quarters. With more transparency into what we’re building, you can also plan better and share feedback earlier to influence what we’re building.
The GitHub public roadmap is a new public repository on GitHub that anyone can access. There, you’ll find a project board that lays out upcoming releases. Each item on the board links to a detailed issue with more information about what we’re planning, why it’s important, when we expect to deliver it, and a bit about how we expect it to work.
For example, if you filter the project board using the “beta”, “server”, and “security & compliance” labels you’ll see which quarter we plan to bring code scanning and secret scanning to GitHub Enterprise Server in beta. You can also watch the repository or subscribe to individual roadmap issues to be notified about changes directly within GitHub.
Historically, GitHub has shared forward-looking product announcements at major events or in the occasional blog post, and we’ll continue to do this. While the public roadmap isn’t exhaustive, it will include most aspects of our product plans, and will be regularly updated.
If you have questions or comments, share them publicly on the GitHub Community Forum or privately via the Share feedback page, as you already do today. We look forward to keeping you informed and to hearing your feedback about what’s on the roadmap.
Besides the content of the roadmap being updated regularly, we’re also planning to iterate on the format of the roadmap itself. We see the potential of reactions, issue comments, and even GitHub Discussions being valuable additions to the repository for receiving direct signals back from the community about what we’ve planned. If you have feedback about the roadmap repository itself, such as how the issues are presented, let us know through this Share feedback page.