👋 We've unified all of GitHub's product documentation in one place! Check out the content for REST API, GraphQL API, and Developers. Learn more on the GitHub blog.

This version of GitHub Enterprise will be discontinued on This version of GitHub Enterprise was discontinued on 2020-08-20. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise. For help with the upgrade, contact GitHub Enterprise support.

Article version: Enterprise Server 2.18

Creating an issues-only repository

GitHub Enterprise does not provide issues-only access permissions, but you can accomplish this using a second repository which contains only the issues.

Were you able to find what you were looking for?

  1. Create a private repository to host the source code from your project.
  2. Create a second repository with the permissions you desire to host the issue tracker.
  3. Add a README file to the issues repository explaining the purpose of this repository and linking to the issues section.
  4. Set your collaborators or teams to give access to the repositories as you desire.

Users with write access to both can reference and close issues back and forth across the repositories, but those without the required permissions will see references that contain a minimum of information.

For example, if you pushed a commit to the private repository's default branch with a message that read Fixes organization/public-repo#12, the issue would be closed, but only users with the proper permissions would see the cross-repository reference indicating the commit that closed the issue. Without the permissions, a reference still appears, but the details are omitted.

Were you able to find what you were looking for?

Ask a human

Can't find what you're looking for?

Contact us