This version of GitHub Enterprise was discontinued on 2020-11-12. 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.

About labels

Labels on GitHub Enterprise Server 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 Server provides default labels in every new repository. You can use these default labels to help create a standard workflow in a repository:

bugIndicates an unexpected problem or unintended behavior
documentationIndicates a need for improvements or additions to documentation
duplicateIndicates similar issues or pull requests
enhancementIndicates new feature requests
good first issueIndicates a good issue for first-time contributors
help wantedIndicates that a maintainer wants help on an issue or pull request
invalidIndicates that an issue or pull request is no longer relevant
questionIndicates that an issue or pull request needs more information
wontfixIndicates 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."