Labels on GitHub Enterprise help you organize and prioritize your work. You can apply labels to issues and pull requests to signify priority, category, or any other information you find useful.
Labels are tied to the repository they are created in. Once a label exists, you can use it on any issue or pull request within that repository. For more information, see "Creating a label."
Anyone with read access to a repository can view and search the repository’s labels. To create, edit, apply, or delete a label, you must have write access to the repository.
Using default labels
GitHub Enterprise provides default labels in every new repository. You can use these default labels to help create a standard workflow in a repository:
||Indicates an unexpected problem or unintended behavior|
||Indicates a need for improvements or additions to documentation|
||Indicates similar issues or pull requests|
||Indicates new feature requests|
||Indicates a good issue for first-time contributors|
||Indicates that a maintainer wants help on an issue or pull request|
||Indicates that an issue or pull request is no longer relevant|
||Indicates that an issue or pull request needs more information|
||Indicates that work won't continue on an issue or pull request|
Default labels are included in every new repository when the repository is created, but you can edit or delete the labels later. For more information, see "Deleting a label."
Organization owners can customize the default labels for repositories in their organization. For more information, see "Managing default labels for repositories in your organization."