Skip to main content
This guide shows how to enable or disable GitHub repository features (Discussions, Projects, Wikis, and Issues) so your repository UI matches your team’s workflow. Follow the steps to hide unused tabs and prevent new items from being created for specific features. Overview
  • Disabling a feature hides its tab from the repository UI and prevents collaborators from creating new items for that feature.
  • You can enable or disable the following features from the repository settings: Discussions, Projects, Wikis, and Issues.
  • Consider the impact on contributors and automation before disabling a feature—Issues and pull requests are commonly used for day-to-day collaboration.
Before making changes, review your team’s workflow and inform collaborators. Disabling features will change how contributors interact with the repository.
What happens when you toggle a feature Step-by-step: Disable (or enable) repository features
  1. Open your repository on GitHub.
  2. Click the repository Settings tab.
  3. In Settings, expand the Options (sometimes labeled “Features”) section and scroll to the Features area.
  4. Use the toggles to enable or disable features:
    • Discussions
    • Projects
    • Wikis
    • Issues
  5. Your changes are typically applied automatically when you toggle an option.
  6. To re-enable a feature later, return to the same toggles and switch them back on.
Quick checklist before toggling repository features Example flow
  • To disable Wikis: go to Settings → Options → Features and flip off the “Wikis” toggle.
  • To remove Discussions and Projects from the repository interface: toggle each off in the same Features area.
  • After toggling, the corresponding tabs no longer appear in the repository header, so contributors will rely on the remaining features (for example, Issues and pull requests) for collaboration.
How to communicate the change
  • Update repository README and CONTRIBUTING.md with the new preferred workflow.
  • Create a pinned issue or send a team announcement explaining where to file bugs, feature requests, and design discussions after the change.
  • Provide links to external trackers or documentation if you migrate content.
Links and references
Disabling features can impact existing workflows and automation. If you rely on integrations or bots that use a feature (for example, Discussions or Wikis), confirm compatibility before disabling it.
Recommendations
  • Most teams keep Issues and Pull Requests enabled because they are central to code review and task tracking.
  • Use the repository settings to tailor available features to your team’s chosen processes.
  • Communicate changes clearly so contributors know where to create and track work.
That’s it — use Settings → Features toggles to enable or disable the UI features that best fit your workflow.

Watch Video