How to Create a Pull Request to Update the 996 ICU Blacklist

Fork the 996icu/996.ICU repository, add the company and evidence to blacklist/README.md, store supporting images in blacklist/img/, commit with a descriptive message, push to your fork, and open a PR against the master branch including the branch SHA-256 in the description.

The 996.ICU repository maintains a community-curated blacklist of companies violating Chinese labor laws regarding excessive overtime. Creating a pull request to update this list requires following a specific workflow defined in the source code to ensure all entries include verifiable evidence and adhere to the strict Markdown table format.

Understanding the Blacklist Structure

Before modifying any files, examine the structure of the blacklist/ directory in the repository root. The blacklist/README.md file contains the master Markdown table listing companies alongside the contribution guidelines, while the blacklist/img/ subdirectory stores screenshot evidence. According to the contribution guidelines in lines 11-20 of the blacklist README, every entry must provide “必要的描述内容及确切证据” (necessary descriptions and exact evidence) to be accepted by maintainers.

Step-by-Step Workflow to Update the Blacklist

1. Fork and Clone the Repository

Start by forking the repository through the GitHub web interface to create a personal copy under your GitHub account. Then clone your fork locally to begin editing.

git clone https://github.com/<your-username>/996.ICU.git
cd 996.ICU

2. Create a Feature Branch

Create a descriptively named branch to isolate your changes from the master branch. This keeps your contribution organized and allows maintainers to review changes in isolation.

git checkout -b update-blacklist-<company-name>

3. Edit the Blacklist Entry

Open blacklist/README.md and locate the Markdown table. Add a new row following the established column order: city, company name (with hyperlink), exposure time, policy description, evidence link, SHA-256 of your branch, and cancel evidence link.

If you have screenshots or documents supporting your claim, place them in blacklist/img/ and reference them using relative Markdown links. The repository requires version-controlled evidence to ensure reproducible history and prevent link rot.

Example table row format:

|北京|[Acme Corp](https://acme.example.com)|2023-09-01|强制996|[证据链接](img/acme_evidence.png)|<branch-sha256>|[取消证据](img/acme_cancel.png)|

4. Commit and Push Your Changes

Stage the modified README and any new images in the blacklist/img/ directory, then commit with a clear message describing the addition. Maintainers prefer atomic commits that group the table update with its corresponding evidence.

git add blacklist/README.md blacklist/img/<company-name>*.png
git commit -m "Add <Company> to blacklist – provide evidence"
git push origin update-blacklist-<company-name>

5. Open the Pull Request

Navigate to the original 996icu/996.ICU repository on GitHub and initiate a new Pull Request. Select your fork's branch as the source and 996icu/996.ICU:master as the target base.

In the PR description, summarize the evidence, link to any external sources, and include the SHA-256 of your branch as required by the PR template. This hash ensures the specific commit history can be cryptographically verified by automated checks and maintainers.

Required Evidence Format

The blacklist maintains strict standards for entry validity to protect both contributors and accused companies. Each submission must include:

• City and company name with a valid corporate URL
• Exposure time documenting when the 996 policy was observed (YYYY-MM-DD format)
• Policy description detailing the specific labor law violations in Chinese
• Evidence links pointing to images stored in blacklist/img/ or external documentation
• Branch SHA-256 for cryptographic verification of your contribution state
• Cancel evidence (optional) providing documentation if the company later rectifies the policy

All images must reside in blacklist/img/ rather than external hosting to remain under Git version control alongside the data table, ensuring the historical record remains immutable and auditable.

Summary

• The 996 ICU blacklist resides in blacklist/README.md as a Markdown table with seven required columns
• Evidence images must be stored in blacklist/img/ and referenced via relative Markdown links
• Contributions require forking the repository, creating a feature branch, and opening PRs against the upstream master branch
• Include the branch SHA-256 in your PR description for cryptographic verification purposes
• Follow the contribution guidelines in lines 11-20 of blacklist/README.md for exact evidence requirements

Frequently Asked Questions

What information must I include when adding a company to the blacklist?

You must provide the city, company name with URL, exposure time, policy description, evidence links, the SHA-256 of your branch, and optionally cancel evidence. According to lines 11-20 of blacklist/README.md, entries lacking “必要的描述内容及确切证据” (necessary descriptions and exact evidence) will be rejected by maintainers during the review process.

Where should I store screenshot evidence for my blacklist entry?

Store all images in the blacklist/img/ directory and reference them using relative Markdown links such as [evidence](img/company_evidence.png). This ensures evidence remains version-controlled within the Git repository and accessible even if external hosting services fail or links break over time.

Why does the pull request require a branch SHA-256?

The SHA-256 hash provides cryptographic verification of your branch's exact state, ensuring the evidence and code reviewed by maintainers matches precisely what you committed. This prevents post-submission tampering and creates an immutable, auditable history for each blacklist entry that can be verified by third parties.

Can I update an existing blacklist entry instead of adding a new one?

Yes. Follow the same pull request workflow, but modify the existing row in blacklist/README.md rather than appending a new one. If updating evidence, place new images in blacklist/img/ and update the relative references in the table row accordingly, ensuring the commit message clearly indicates you are modifying an existing entry rather than adding a new company.

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