The Wayback Machine - https://web.archive.org./web/20201027163949/https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/about-labels

About labels

Labels on GitHub 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.

In this article

Did this doc help you?

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

Or, learn how to contribute.

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

LabelDescription
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."

Organization owners can customize the default labels for repositories in their organization. For more information, see "Managing default labels for repositories in your organization."

Further reading

Did this doc help you?

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

Or, learn how to contribute.