Add a role or a permission level that gives a user access to issues, without giving them any access to the source code. The newly added triage role is a step in the right direction but it also gives read-only access to the code.
The recommended way to do that as of January 2020 is to create a separate issues-only repository, but if you do that then your commit messages have to reference issues by using the long notation (organization/project#123), which is a major inconvenience.
Use case:
A game development company with external testers. Those testers are often outsourced, or they are selected from the community. In either case you do not want to give them access to the source code.
Add a role or a permission level that gives a user access to issues, without giving them any access to the source code. The newly added triage role is a step in the right direction but it also gives read-only access to the code.
The recommended way to do that as of January 2020 is to create a separate issues-only repository, but if you do that then your commit messages have to reference issues by using the long notation (
organization/project#123), which is a major inconvenience.Use case:
A game development company with external testers. Those testers are often outsourced, or they are selected from the community. In either case you do not want to give them access to the source code.