How to Submit a Project to the 996.ICU Awesome List: A Complete Guide

Submitting a project to the 996.ICU awesomelist requires editing the awesomelist/README.md file to add a properly formatted row to the markdown table, ensuring your project uses the Anti-996 License and includes a 60×60 pixel logo.

The 996.ICU repository maintains a curated awesome list of projects that have adopted the Anti-996 License to protest excessive working hours. If you want to submit your open-source project to this list, you must follow a specific contribution format defined in the repository's markdown files.

Prerequisites for Submitting to the Awesomelist

Before you submit a project, verify that your repository meets the mandatory licensing requirement. The 996.ICU awesomelist exclusively features projects that use the Anti-996 License or derivatives of it.

According to the contribution guidelines in awesomelist/README.md, your project must reference the license badge using the specific URL pattern pointing to the main repository's LICENSE file. The standard format uses a shields.io badge linking to https://github.com/996icu/996.ICU/blob/master/LICENSE.

Step-by-Step Guide to Submit a Project

Locate the Contribution Guidelines

Navigate to the awesomelist/README.md file in the 996.ICU repository. The first section of this file contains the formatting rules and field requirements for new entries.

The guide specifies two critical formatting constraints:

• Logo dimensions must be exactly 60 × 60 pixels, inserted using HTML-style image tags with width="60" attributes
• Official homepage links must follow the pattern [GitHub](url) for repository links or [Official](url) for project websites

Format Your Project Entry

Prepare your entry data according to the six-column table structure. Each row in awesomelist/README.md uses pipe-separated markdown table syntax with the following columns: LOGO, 项目 (Project), 官网 (Official Website), Stars, 简介 (Introduction), and License.

For the LOGO column, use this exact format:

<img src="https://your-domain.com/logo.png" width="60">

For the License column, include the Anti-996 badge:

[![LICENSE](https://img.shields.io/badge/license-Anti%20996-blue.svg)](https://github.com/996icu/996.ICU/blob/master/LICENSE)

Add Your Row to the Markdown Table

Insert your formatted row into the existing table in awesomelist/README.md. The table typically appears around lines 15-20 in the file, following the header row that defines the column structure.

Maintain consistent pipe formatting with leading and trailing pipes for each row. Your entry should align vertically with existing entries to ensure proper markdown table rendering.

Example of a complete table row:

| <img src="https://example.com/logo.png" width="60"> | [My-Awesome-Project](https://github.com/user/my-awesome-project) | [GitHub](https://github.com/user/my-awesome-project) / [Official](https://myawesome.com) | ![](https://img.shields.io/github/stars/user/my-awesome-project) | A brief description of what the project does. | [![LICENSE](https://img.shields.io/badge/license-Anti%20996-blue.svg)](https://github.com/996icu/996.ICU/blob/master/LICENSE) |

Submit Your Pull Request

Commit your changes to a feature branch and open a Pull Request against the master branch of the 996.ICU repository. The maintainers will review your submission for compliance with the formatting guidelines and license requirements before merging.

Understanding the Table Structure in awesomelist/README.md

The awesome list uses a markdown table with strict column ordering. Here is the breakdown of each column's requirements:

Column	Content Requirements	Example
LOGO	60×60px image using <img> tag with width="60"	<img src="logo.png" width="60">
项目	Project name as a markdown link to the repository	[Project-Name](https://github.com/user/repo)
官网	One or more links separated by /	[GitHub](url) / [Official](url)
Stars	Shields.io badge showing GitHub stars	
简介	One-sentence description (Chinese or English)	A CLI tool for automating workflows
License	Anti-996 license badge linking to 996.ICU LICENSE file	[](https://github.com/996icu/996.ICU/blob/master/LICENSE)

Summary

• Submitting to the 996.ICU awesomelist requires editing awesomelist/README.md to add a new row to the markdown table.
• Your project must use the Anti-996 License and include the corresponding badge in the License column.
• Logos must be exactly 60×60 pixels and inserted using <img> tags with width="60" attributes.
• Follow the pipe-separated table format with columns: LOGO, 项目, 官网, Stars, 简介, and License.
• Submit your changes via a Pull Request to the master branch for maintainer review.

Frequently Asked Questions

What license must my project use to be included in the awesomelist?

Your project must adopt the Anti-996 License or a derivative that prohibits 996 working hour practices. The License column in your table entry must link to the official license file in the 996.ICU repository using the shields.io badge format specified in the contribution guidelines.

Can I submit a project to the awesomelist without a logo?

No. The contribution guidelines in awesomelist/README.md explicitly require a logo for every entry. The logo must be exactly 60×60 pixels and formatted using an HTML <img> tag with the width="60" attribute to ensure consistent table rendering across different markdown viewers.

How long does the review process take for awesomelist submissions?

The review timeline depends on maintainer availability. Since 996.ICU is a community-driven open-source project, pull requests are reviewed manually to verify license compliance and formatting accuracy. Ensure your submission follows the exact table structure and logo specifications to avoid delays from revision requests.

Where exactly should I add my project in the awesomelist/README.md table?

Add your project as a new row within the existing markdown table, typically following the header row and continuing the sequence of existing entries. The table structure begins around line 15 in the file. Insert your pipe-separated row in the same format as surrounding entries to maintain table integrity, without modifying the column header row.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}