How to Report Incorrect Information on the 996.ICU Blacklist
To report incorrect information on the 996.ICU blacklist, fork the repository, edit blacklist/README.md to correct or remove the erroneous entry, and submit a pull request with supporting evidence.
The 996.ICU project maintains a community-driven blacklist documenting companies that violate Chinese labor law overtime limits. If you discover inaccurate entries—whether due to outdated evidence, mistaken identity, or incorrect descriptions—you can report incorrect information on the blacklist through the repository's standardized GitHub contribution workflow.
Locate the Blacklist Source File
All blacklist data resides in blacklist/README.md on the repository's master branch. This file contains the Contribution Guide (lines 11–31) that specifies what every correction must include: a textual description of the change, a reliable evidence link (or screenshot uploaded to blacklist/img/), and confirmation that personal data has been removed from any images.
The actual blacklist tables begin at line 44, where each company entry appears as a row in Markdown table format.
Prepare Your Correction
Fork and Branch the Repository
Start by creating your own copy of the repository and a dedicated branch for the fix:
# Fork the repo on GitHub, then clone your fork
git clone https://github.com/<your-username>/996.ICU.git
cd 996.ICU
# Create a branch for the correction
git checkout -b fix-incorrect-entry
Edit the Blacklist Entry
Open blacklist/README.md and locate the table row containing the incorrect information. Depending on the error type, either update the row with corrected details or remove it entirely.
If you are removing an entry because the company no longer practices 996 hours, add a corresponding row to the "已取消996名单列表" (canceled list) table with a brief reason and supporting evidence:
|北京|[字节跳动](https://bytedance.com)|2021年|误报|[原证据链接](https://example.com/evidence)|
Handle Evidence and Screenshots
When reporting incorrect information, you may need to provide new evidence or corrected documentation:
- Save screenshots to
blacklist/img/using descriptive filenames - Ensure all personal identifiers (names, employee IDs, faces) are blurred or redacted per the contribution guidelines (lines 21–23)
- Reference the image in your README.md edit using a relative path
Stage both the documentation and image files together:
git add blacklist/README.md blacklist/img/<new-image>.png
git commit -m "Fix incorrect blacklist entry for XXX company – wrong evidence"
git push origin fix-incorrect-entry
Submit a Pull Request to Report the Issue
Once your branch is pushed, open a Pull Request against 996icu/996.ICU:master:
- Use a clear title such as "Fix: Remove incorrect entry for [Company Name]"
- In the description, explicitly state that you are correcting erroneous blacklist information
- Link to the relevant evidence (the project automatically archives external URLs via the Internet Archive, so include original URLs when possible)
- Explain why the original entry was incorrect (outdated, mistaken identity, etc.)
Maintainers review PRs for evidence quality and accuracy. Once verified, they merge the correction, and the updated blacklist appears immediately at https://github.com/996icu/996.ICU/blob/master/blacklist/README.md.
Summary
- Report incorrect blacklist information by editing
blacklist/README.mdand submitting a pull request to the 996.ICU repository. - Locate entries starting at line 44 of the blacklist file, following the contribution guidelines in lines 11–31.
- Provide evidence by uploading redacted screenshots to
blacklist/img/and referencing them in your edit. - Use the canceled list ("已取消996名单列表") when removing entries to maintain historical transparency.
- Archive links via the Internet Archive to ensure evidence remains accessible even if original sources change.
Frequently Asked Questions
What types of errors should I report on the 996.ICU blacklist?
You should report any entry where the company no longer enforces 996 working hours, where the evidence is outdated or fabricated, where the company name is incorrect, or where the description misrepresents the working conditions. The maintainers prioritize corrections that include verifiable evidence such as updated labor contracts, company announcements, or reliable media reports.
Do I need programming skills to report incorrect blacklist information?
No programming knowledge is required. The blacklist is maintained as a Markdown table in blacklist/README.md, which you can edit directly through GitHub's web interface. You only need a GitHub account to fork the repository, edit the file, and submit a pull request. However, using Git commands locally (as shown in the examples above) provides more control over the process.
How long does it take for corrections to be merged?
Merge times vary based on maintainer availability and the complexity of the evidence provided. Simple corrections with clear, archived evidence typically merge within days. Disputed entries requiring additional verification or community discussion may take longer. The project encourages contributors to respond promptly to maintainer feedback in the pull request comments to expedite the process.
What evidence is required when reporting incorrect information?
You must provide reliable evidence that contradicts the original blacklist entry. Acceptable evidence includes official company policy documents, updated labor contract screenshots (with personal data redacted), credible news articles, or links to government labor bureau records. Upload screenshots to blacklist/img/ and reference them in your pull request. The project automatically archives external URLs via the Internet Archive, so include original source links whenever possible.
Have a question about this repo?
These articles cover the highlights, but your codebase questions are specific. Give your agent direct access to the source. Share this with your agent to get started:
curl -s "https://instagit.com/install.md" Maintain an open-source project? Get it listed too →