Deprecating Outdated Issues on the GitHub Public Roadmap · github roadmap · Discussion #1014

6 min read Original article ↗

Deprecating Outdated Issues on the GitHub Public Roadmap

At GitHub, transparency and clarity are at the heart of our relationship with the community. As part of our ongoing efforts to keep you informed about our product roadmap, we’ve already begun hosting quarterly roadmap webinars to share updates and engage with the community in real-time.

This week, we’re taking the next step in achieving our roadmap goals by refreshing the public roadmap project board.

After an in-depth review, we’ve identified a number of open issues that have become outdated over time—some for several years. To better align with our current product direction and to build trust with our users, we are deprecating these outdated issues and updating the board with new and accurate information.

This refresh will make it easier for you to follow our progress, ensure higher-quality updates, and provide a more accurate reflection of GitHub’s development priorities. Moving forward, we are also committing to regular updates, so you can rely on the roadmap as a trusted source of information about GitHub’s ongoing and upcoming features.

What’s Changing?

  • Deprecation of Outdated Issues: We will be removing a number of issues that are no longer relevant due to changes in priorities or project timelines. These issues have been stagnant and no longer represent our product direction.
  • Full Board Refresh: A complete update to the roadmap board will be made, adding new features and plans that better reflect where GitHub is headed.
  • Ongoing Maintenance: To ensure the roadmap stays accurate, we will be conducting regular reviews and updates.

FAQ

Why are we deprecating these issues?

  • Many of the issues marked for deprecation are out of date and no longer align with GitHub’s current roadmap. By cleaning up the board, we aim to provide more accurate, actionable insights to the community.

What can I expect from the refreshed roadmap?

  • The refreshed roadmap will feature up-to-date information about new initiatives and priorities. Our goal is to make the roadmap a reliable resource that users can check regularly for accurate and relevant details.

Will the roadmap be updated regularly?

  • Yes! We’re committing to regularly updating the roadmap to ensure it reflects the latest developments. This is part of our effort to build and maintain trust with our community.

What should I do if an issue I care about is deprecated?

  • While some issues may no longer be represented in the public roadmap, we are always listening to community feedback. If you have concerns about a specific feature or request, feel free raise your thoughts in the discussions.

Deprecated Issues

As part of this update, the following issues will be deprecated. If you have questions on a specific issue/roadmap item, please reach out to your GitHub contact.

Deprecated Issue
Command Palette [GA]
GitHub Actions: Secure Shell Debugging (Beta)
Actions: Managing Environments at Scale
GitHub Actions: Artifacts v4 available in GitHub Enterprise Server
Precise code navigation for Java
Precise code navigation for JavaScript and TypeScript
Issue level custom metadata
Ability to add a project to a project
Cross repository milestones and labels
Create custom automation flows
Projects: Activity History
Projects: Updated Projects header
[Public Beta] Issue Hierarchy powered by Tasklists
Packages: Granular permissions and easy organization sharing for enterprise customers
Packages: maven - granular permissions and easy organization sharing
GitHub Actions secrets improvements for Reusable workflows [GA]
More control over required status checks for pull requests using merge queue
Reply to PR-level comments
Codespaces: Pull Request Validation for prebuild-enabled repositories
Pull Request Dashboard
Dependabot on Actions Forced Migration
Secret scanning push protection for gists
Secret scanning: Extend coverage to Actions logs
Dependabot alerts shows transitive dependency paths
GHES Cluster High Availability
Open ID Connect (OIDC) for GHEC Audit Log Streaming to Azure Blob Storage
Azure AD (AAD) Service Principal Support for GHEC EMUs (Beta)
GitHub Actions Starter workflow improvements
Automatic security check information on each Actions listing
Actions: Private networking for GitHub-hosted macOS runners
Security manager improvements and custom organization security roles (Preview)
Expanding access to historical log data via audit log exports (Preview)
Code security transaction report in PDF
Code scanning: AI-powered autofixes for CodeQL alerts integrated into VS Code
Increase GitHub Enterprise Importer's (GEI) repository size limit to 40GB (Preview)
Enterprise Apps and installation automation (Public Beta)
GitHub Security Advisory private forks support Actions
GitHub Actions configuration variables - GA
Actions: Outbound network control for GitHub-hosted runners
Enterprise access for GitHub apps
Codespaces: Private networking with Azure VNETs (Preview)
Commenting on unchanged lines in a pull request

We appreciate your understanding as we make these changes. Our aim is to keep you better informed and involved in our development process. Thank you for being a valued member of the GitHub community!


📰 Update: Nov 26, 2024

Hi GitHub Community! 👋

We know some of you are disappointed to see certain items removed from our public roadmap, and we really appreciate your feedback. Your input means a lot to us, and these changes reflect some tough prioritization decisions we’ve had to make to focus on delivering the most impactful solutions for everyone.

We first want to apologize for a slightly misleading statement we made in our original post, that we hope to acknowledge and correct. We said that the closed issues no longer represent our product direction, however there are a number of reasons for removal, from the feature not being aligned with our strategic priorities, to our desire to actively acknowledge uncertainty on the timeline for a feature and remove it until we have more certainty.

In order to provide that missing clarity, we are adding more comments to the list of issues above with more details about why they were removed and whether there’s something similar on our refreshed roadmap. You’ll see those comments added over the next couple of weeks. While not everything will return to the roadmap, we’re dedicated to staying open, honest, and to regularly updating you. Look out for our next roadmap update in January—we’re excited to share the new possibilities we’re working on!

We invite you to keep the conversation going in our Community. It’s the best place to share your feedback, ask questions, and connect with our team and other users. Your thoughts play a big role in shaping what we do, and we’re here to listen and collaborate with you to make GitHub the best it can be.