How to Contribute Evidence to the Company Blacklist in 996.ICU

To contribute evidence to the company blacklist, prepare sanitized external links or internal screenshots, add a formatted row to the markdown table in blacklist/README.md, and submit a Pull Request for maintainer review.

The 996.ICU repository maintains a public blacklist documenting companies that enforce illegal "996" overtime practices (9 a.m.–9 p.m., 6 days per week). Contributing new evidence follows a structured workflow defined in the blacklist documentation at blacklist/README.md【/cache/repos/github.com/996icu/996.ICU/master/blacklist/README.md#L11-L23】. This guide explains how to properly format and submit evidence while ensuring privacy compliance and long-term accessibility.

Evidence Categories and Preparation

The repository accepts two distinct categories of evidence. Proper preparation ensures your submission meets the legal and technical standards required for inclusion.

External Evidence

External evidence includes official company announcements, news articles, and recruitment-site descriptions that document overtime policies. For this category, simply provide the URL to the public source【/cache/repos/github.com/996icu/996.ICU/master/blacklist/README.md#L14-L17】. No local file hosting is required, as these links are automatically archived.

Internal Evidence

Internal evidence consists of screenshots from internal forums, emails, punch-card records, or compensatory-off logs. Upload these images to the blacklist/img/ directory and reference them using a relative path such as img/company-evidence.png. If you prefer not to host the image directly in the repository, include the screenshot link in the Pull Request description instead【/cache/repos/github.com/996icu/996.ICU/master/blacklist/README.md#L17-L20】.

Data Sanitization Requirements

Before uploading any screenshot, scrub all personal identifiers including employee names, IDs, phone numbers, and email addresses. The documentation specifically recommends using a "screen-capture" method rather than direct downloads to avoid embedded digital watermark tracking that could expose the source【/cache/repos/github.com/996icu/996.ICU/master/blacklist/README.md#L21-L22】.

Submitting Your Contribution

Contributions are submitted via GitHub Pull Requests that modify the central blacklist table.

Editing the Blacklist Table

Create a new branch and edit the markdown table located in the "名单列表" section of blacklist/README.md. Each row requires five columns: city, company name (with URL), exposure/implementation date, description of the overtime regime, and the evidence link or image path.

For external evidence, use a standard markdown link:

|北京|[字节跳动](https://www.bytedance.com)|2020-03-01|强制996|[媒体报道](https://www.example.com/news/byte-dance-996)|

For internal screenshot evidence, use the relative image path:

|深圳|[某科技公司](https://www.example.com)|2021-06-15|大小周、每日加班3h|![打卡截图](img/techco-punch-20210615.png)|

Git Workflow Commands

Execute the following commands to stage your changes locally:

git clone https://github.com/996icu/996.ICU.git
cd 996.ICU

# Copy your sanitized screenshot to the evidence directory

cp ~/Downloads/screenshot.png blacklist/img/company-evidence.png

# Edit the blacklist table with your new row

vim blacklist/README.md

# Commit and push your changes

git checkout -b add-company-evidence
git add blacklist/README.md blacklist/img/company-evidence.png
git commit -m "Add evidence for Company X (size-week, 996)"
git push origin add-company-evidence

# Open a PR on GitHub describing the evidence source

Automated Archiving and Review Process

Once your PR is merged, all external URLs are automatically submitted to the Internet Archive for long-term persistence【/cache/repos/github.com/996icu/996.ICU/master/blacklist/README.md#L23-L24】. If the original link later becomes inaccessible, the archived version remains retrievable.

Maintainers review submissions to verify legal compliance, evidence clarity, and the absence of personal data before merging【/cache/repos/github.com/996icu/996.ICU/master/blacklist/README.md#L27-L30】. Only accepted entries appear in the public blacklist table.

Summary

• Prepare evidence as either external URLs or internal screenshots placed in blacklist/img/.
• Sanitize all personal data from screenshots to protect individual privacy.
• Edit blacklist/README.md to add a properly formatted row to the markdown table.
• Submit a Pull Request and wait for maintainer verification before the entry goes live.
• Automatic archiving preserves external links via the Internet Archive after merge.

Frequently Asked Questions

What types of evidence are accepted for the company blacklist?

The repository accepts external evidence (public URLs to news articles or official announcements) and internal evidence (screenshots of punch-card systems, internal emails, or HR documents). External links require no file upload, while internal screenshots must be placed in the blacklist/img/ directory【/cache/repos/github.com/996icu/996.ICU/master/blacklist/README.md#L14-L20】.

How do I sanitize screenshots before submitting?

Remove all personal identifiers including employee names, IDs, phone numbers, and email addresses from the image. Use screen-capture methods rather than downloading originals to avoid digital watermark tracking that could identify the source【/cache/repos/github.com/996icu/996.ICU/master/blacklist/README.md#L21-L22】.

Where do I place image files when contributing evidence?

Upload sanitized screenshot files to the blacklist/img/ directory and reference them in the markdown table using relative paths like img/filename.png. If you cannot host the image in the repository, provide the link in the Pull Request description instead【/cache/repos/github.com/996icu/996.ICU/master/blacklist/README.md#L17-L20】.

What happens after I submit a Pull Request?

Maintainers review your submission for legal compliance, evidence quality, and privacy sanitization. Once approved and merged, external links are automatically archived to the Internet Archive, and the company appears in the public blacklist table【/cache/repos/github.com/996icu/996.ICU/master/blacklist/README.md#L23-L30】.

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