Disabling projects
Not every team manages their work on GitHub in the same way. Now you can disable repository and organization-wide Projects if you’re not using them. Users with admin privileges on…
Not every team manages their work on GitHub in the same way. Now you can disable repository and organization-wide Projects if you’re not using them.
Users with admin privileges on a repository can disable Projects by navigating to that repository’s settings and unchecking the “Projects” box. Similarly, organization owners can disable Projects by navigating to an organization’s settings and clicking “Projects” in the sidebar. On this page, unchecking the “Enable Projects for the organization” box will disable organization-wide Projects, and unchecking the “Enable Projects for all repositories” box will disable Projects for all repositories in the organization.
Disabling Projects hides the Projects tab from the repository and organization navigation, removes Projects from Issue and Pull Request sidebars, and hides Project-related events from Issue timelines. Disabled Projects are also inaccessible via API requests.
Projects can be re-enabled at any time, at which point all previously-disabled projects will be restored exactly as you left them.
Check out the help documentation and the Projects API page to learn more.
Written by
Related posts
GitHub Availability Report: October 2025
In October, we experienced four incidents that resulted in degraded performance across GitHub services.
TypeScript, Python, and the AI feedback loop changing software development
An interview with the leader of GitHub Next, Idan Gazit, on TypeScript, Python, and what comes next.
What 986 million code pushes say about the developer workflow in 2025
Nearly a billion commits later, the way we ship code has changed for good. Here’s what the 2025 Octoverse data says about how devs really work now.