# GitHub Topics Recommended for an Awesome List Repository: Required Tags Explained > Discover essential GitHub topics like awesome-list and awesome for your awesome list repository. Boost discoverability and meet submission requirements with these crucial tags. - Repository: [Sindre Sorhus/awesome](https://github.com/sindresorhus/awesome) - Tags: best-practices - Published: 2026-07-07 --- **Every awesome list repository must include the `awesome-list` and `awesome` GitHub topics to meet submission requirements and ensure discoverability in curated collections.** The sindresorhus/awesome repository maintains strict quality standards for curated lists across the GitHub ecosystem. According to the project's contribution guidelines, properly tagging your repository is mandatory before submitting a pull request. These specific GitHub topics recommended for an awesome list repository help users discover your collection through GitHub's topic search and the central "All Awesome Lists" index. ## Why These Topics Are Required The repository's contribution checklist explicitly mandates topic tagging to maintain consistency across the awesome ecosystem. In [`pull_request_template.md`](https://github.com/sindresorhus/awesome/blob/main/pull_request_template.md) at line 66, the checklist states: "The repo should have `awesome-list` & `awesome` as GitHub topics." This requirement ensures that maintainers can automatically filter and discover new lists while helping users browse related collections via GitHub's topic search functionality. The main [`readme.md`](https://github.com/sindresorhus/awesome/blob/main/readme.md) file references these topics directly, providing a link to the "All Awesome Lists" GitHub topic page at line 882. This connection demonstrates how the `awesome` and `awesome-list` tags power the discoverability system that connects hundreds of curated collections. ## The Two Required GitHub Topics ### `awesome-list` The `awesome-list` topic signals that your repository follows the specific formatting and quality standards defined by the sindresorhus/awesome project. This tag distinguishes curated awesome lists from general repositories that might contain the word "awesome" in their description but do not follow the community guidelines. ### `awesome` The `awesome` topic marks your repository as part of the broader *awesome* ecosystem. When combined with `awesome-list`, this dual-tagging system ensures your collection appears in both general awesome searches and specific awesome-list filtered views. ## How to Add These Topics to Your Repository You can add the required GitHub topics using three different methods depending on your workflow and automation needs. ### Using the GitHub Web UI 1. Navigate to your repository on GitHub. 2. Click **Settings** → **Options** → **Topics**. 3. Type `awesome-list` and press **Enter**. 4. Type `awesome` and press **Enter**. 5. Click **Save changes**. ### Using the GitHub CLI ```bash # Replace / with your repository name gh repo edit / --add-topic awesome-list --add-topic awesome ``` ### Using the GitHub API ```bash curl -X PATCH \ -H "Authorization: token " \ -H "Accept: application/vnd.github.mercy-preview+json" \ https://api.github.com/repos///topics \ -d '{"names":["awesome-list","awesome"]}' ``` > **Note:** You must have write permissions on the repository to modify its topics. ## Source Files and Validation The requirement for these specific GitHub topics is documented in several key files within the sindresorhus/awesome repository: - **[`pull_request_template.md`](https://github.com/sindresorhus/awesome/blob/main/pull_request_template.md)** (line 66): Contains the mandatory checklist item requiring both topics before submission. - **[`readme.md`](https://github.com/sindresorhus/awesome/blob/main/readme.md)** (line 882): References the "All Awesome Lists" topic page, demonstrating how these tags enable discoverability. - **[`create-list.md`](https://github.com/sindresorhus/awesome/blob/main/create-list.md)**: Provides guidance for contributors preparing new lists, including verification steps to check for duplicates before adding topics. ## Summary - **Required topics**: Every awesome list must include both `awesome-list` and `awesome` as GitHub topics. - **Validation location**: The requirement is explicitly stated in [`pull_request_template.md`](https://github.com/sindresorhus/awesome/blob/main/pull_request_template.md) at line 66. - **Discoverability**: These tags enable inclusion in GitHub's "All Awesome Lists" topic search and the main repository's curated index. - **Implementation methods**: Topics can be added via the GitHub web interface, GitHub CLI, or REST API. ## Frequently Asked Questions ### What happens if I don't add these topics to my awesome list? Pull requests to the sindresorhus/awesome repository will not be accepted without these topics. The contribution checklist in [`pull_request_template.md`](https://github.com/sindresorhus/awesome/blob/main/pull_request_template.md) explicitly requires both tags as a mandatory prerequisite, and maintainers verify their presence before merging submissions. ### Can I add additional topics beyond `awesome` and `awesome-list`? Yes. While `awesome` and `awesome-list` are the only required GitHub topics recommended for an awesome list repository, you should add relevant descriptive topics (such as `python`, `machine-learning`, or `web-development`) to improve searchability within your specific domain. ### Does the order of topics matter when adding them via the API? No. The GitHub API accepts the topics array in any order, and the web interface displays topics alphabetically. Both `awesome-list` and `awesome` must be present in the array, but their position in the JSON payload does not affect functionality. ### Where can I verify that my topics were added correctly? You can verify your repository's topics by visiting the repository's main page on GitHub and looking at the "About" section on the right sidebar. Alternatively, query the API endpoint `https://api.github.com/repos///topics` to retrieve the current topic list programmatically.