HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
github
roadmap
OPEN SOURCE2020–2026
github / roadmap

roadmap

GitHub public roadmap

52Distinct people
66Mentions
0Explicit recommenders
9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

GitHub public roadmap

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 7:56:55 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year66 dated mentions

Observed mentions: 2020-07-28 16:13:38 UTC to 2026-04-02 19:17:03 UTC.

0510152020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 15 mentions; 2 submissions, 13 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 15 mentions; 4 submissions, 11 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 14 mentions; 3 submissions, 11 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 9 mentions; 3 submissions, 6 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 8 mentions; 1 submissions, 7 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC15213
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC15411
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC14311
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC321
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC936
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC817
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC211

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
GitHub public roadmap ❇️ View the official GitHub public product roadmap[^1] Our product roadmap is where you can learn about what features we're working on, what stage they're in, and when we expect to bring them to you. Have any questions or comments about items on the roadmap? Share your feedback via GitHub public feedback discussions. The roadmap repository is for communicating GitHub’s roadmap. Existing issues are currently read-only, and we are locking conversations, as we get started. Interaction limits are also in place to ensure issues originate from GitHub. We’re planning to iterate on the format of the roadmap itself, and we see potential to engage more in discussions about the future of GitHub products and features. If you have feedback about this roadmap repository itself, such as how the issues are presented, let us know through general feedback in GitHub public feedback discussions. Guide to the roadmap Every item on the roadmap is an issue, with a label that indicates each of the following: A release phase that describes the next expected phase of the roadmap item. See below for a guide to release phases. A feature area that indicates the area of the product to which the item belongs. For a list of current product areas, see below. A feature that indicates the feature or product to which the item belongs. For a list of current features, see below. One or more product SKU labels that indicate which product SKUs we expect the feature to be available in. For a list of current product SKUs, see below. One or more deployment models (cloud, server, and/or ae). Where not stated, features will generally come out Cloud first, and follow on Server and GHAE at or soon after GA. Once a feature is delivered, the shipped label will be applied to the roadmap issue and the issue will be closed with a comment linking to the relevant Changelog post. Release phases Release phases indicate the stages that the product or feature goes through, from early testing to general availability. preview: Publicly available in full or limited capacity Features mostly complete and documented. Timeline and requirements for GA usually published. No SLAs or support provided. ga: Generally available to all customers Ready for production use with associated SLA and technical support obligations. Approximately 1-2 quarters from Preview. Some of our features may still be in the exploratory stages, and have no timeframe available. These are included in the roadmap only for early feedback. These are marked as follows: in design: Feature in discovery phase. We have decided to build this feature, but are still figuring out how. exploring: Feature under consideration. We are considering building this feature, and gathering feedback on it. Release phases - For GHES Some features may be marked with a GHES 3.X label, which indicates that the feature will also become available for Github Enterprise Server customers. Below are the release version numbers and expected release quarters (Note: these dates are subject to change). GHES release version dates: Version Number Release Quarter Release Notes 3.12 Q1 2024 Release Notes 3.13 Q2 2024 Release Notes 3.14 Q3 2024 Release Notes 3.15 Q4 2024 -- Roadmap stages The roadmap is arranged on a project board to give a sense for how far out each item is on the horizon. Every product or feature is added to a particular project board column according to the quarter in which it is expected to ship next. Be sure to read the disclaimer below since the roadmap is subject to change, especially further out on the timeline. You'll also find an Exploratory column, which is used in conjunction with the in design and exploring release phase labels for when no timeframe is yet available. GitHub Enterprise Server has major releases on a quarterly basis, and minor releases on a monthly basis. Once we know what version we are delivering a feature, we will update the issue to indicate that information. Feature Areas The following is a list of our current product areas: code: Code experiences (Repositories, Pull Requests, Gists) planning: Planning and tracking tools (Issues, Projects) code-to-cloud: Code-to-cloud DevOps (Actions, Packages) collaboration: Collaboration features (Pages, Wikis, Discussions) security & compliance: Code security and compliance features admin-server: Administrative features specific to GitHub Enterprise Server admin-cloud: Administrative features specific to GitHub Cloud communities: Community and social features ecosystem: Ecosystem and API features learning: Education and learning features insights: Continuous learning and insights features client-apps: Client applications (Desktop, Mobile) other: Other features Feature The following is a list of our current features and products, with distinct labels for filtering: actions: GitHub Actions docs: GitHub Docs packages: GitHub Packages pages: GitHub Pages More labels will be added in the future as needed. Product SKUs The following is a list of our current product SKUs. all: Available to all users, including a free tier. Different SKUs may have different levels of functionality. github team: GitHub Team github enterprise: GitHub Enterprise (Cloud and Server) github one: GitHub One (Cloud and Server) github ae: GitHub AE (GHAE) github advanced security: GitHub Advanced Security (add-on to GHE) github insights: GitHub Insights (add-on to GHE) github learning lab: GitHub Learning Lab (add-on to GHE) Disclaimer Any statement in this repository that is not purely historical is considered a forward-looking statement. Forward-looking statements included in this repository are based on information available to GitHub as of the date they are made, and GitHub assumes no obligation to update any forward-looking statements. The forward-looking product roadmap does not represent a commitment, guarantee, obligation or promise to deliver any product or feature, or to deliver any produ
Read the full README on GitHub

What Hacker News says

15 sources
On gitlab, there has been another way for some time: There is a JWT token CI_JOB_JWT available in an env var which contains the branch name and other info as one of the claims [1]. One can then use this token to obtain production secrets based on whether the branch is trusted. Github has the same feature upcoming [2], which allows to get also directly AWS or GCP credentials restricted by branch name [3, 4]. [1] https://docs.gitlab.com/ee/ci/examples/authenticating-with-h... [2] https://github.com/github/roadmap/issues/249 [3] https://awsteele.com/blog/2021/09/15/aws-federation-comes-to... [4] https://github.com/sethvargo/oidc-auth-google-cloud
In Anatomy of a Cloud Infrastructure Attack via a Pull Request
Absolutely agree. Docs are either perfect (5%) or…completely obscure (95%). I can't tell the difference between Github Actions and API documentation in places, but I desire functional examples. No clue where I built it up, but I'm comfortable now…lots of trial and error. For a lot of Github Actions, I actually follow the Github Roadmap through to implementation as the PRs actually have good examples in them… https://github.com/github/roadmap/projects/1
In GitHub Actions limitations and gotchas
Thanks for taking the time to share your experience. I work on GitHub Actions and am familiar with the limitations you're experiencing. Below is more info on where we're at with each of these issues, using the numbers in your Table of Contents. Also, we have a lot of other new things planned for Actions as you can see in our roadmap. https://github.com/github/roadmap/projects/1?card_filter_que... 2.1 We're starting work on this in the next couple of months. We plan to ship it in early 2022. 2.2 We want to speed up the pace of GitHub Enterprise Server releases, but I don't have more info to share. 2.3 We're looking at ways to not require a GHEC account or "unified" license. 2.4 The limits are much higher with the GitHub hosted runners, but this is a current limit of self-hosted runners. 3.1 It's on our backlog. No date to share. 3.2 I have
Read the rest
n't heard this before and thanks for sharing the scenario. We'll think about it. 3.3 This will ship in October. 3.4 We're doing some performance optimizations for GHES 3.4 that should fix this. 3.5 This shipped recently - https://github.blog/changelog/2021-08-25-github-actions-redu... 3.6 We have a couple API improvements coming later this year. 3.7 We're looking into this, but no dates to share. We're dedicated to making Actions a great experience. As you would assume, I'm very excited about the future of Actions and getting feedback like this helps us make it better.
In GitHub Actions limitations and gotchas
The cache action section focuses on GHES which is a shame, since the GitHub.com cache action is also pretty bad. - can't manually delete cache (although they're considering changing that[0]) - only saves cache at the end of a workflow, and only if the workflow succeeds. This could be solved with CircleCI's approach of having a save-cache step and a restore-cache step. - Cache is super slow for self-hosted runners, so it makes more sense to have a local cache instead of using the action - only 5gb of storage size. This was supposed to be increased via billable cache storage[1], but it's been on the backburner since July 2020 - In addition to the above, you can't use a different storage backend on the official action (which would allow storing over 5GB of cache via your own storage). The best workaround is to use a user-provided action whic
Read the rest
In GitHub Actions limitations and gotchas
Dependabot PM following up a few days late > Is there an option to tell dependabot "make one PR per week at most ... You can set the `open-pull-requests-limit: 1` (https://docs.github.com/en/code-security/supply-chain-securi...) and the `schedule.interval: weekly` to limit the number of created PRs to one per week > ... and bundle your changes"? We've referred to this feature as "grouped updates" and it's tracked on the roadmap: https://github.com/github/roadmap/issues/148 Potentially using `allow: direct` (https://docs.github.com/en/code-security/supply-chain-securi...) to ignore the random sub dependencies, or ignoring minor versions (https://docs.github.com/en/code-security/supply-chain-securi...) of some/all dependencies might help reduce that noise.
In Bringing supply chain security features to the Go community

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.