What agents should know before contributing
microsoft/typescript-go
Staging repo for development of native port of TypeScript
Read by Bluet from 1 files written for agents and 300 merged pull requests on 2026-09-24. Not reviewed by the maintainers.
Rules its files tell agents (3)
- CONTRIBUTING.md
shouldDo not open pull requests against this repository as part of a bulk or queue-driven workflow (iterating over i…
Do not open pull requests against this repository as part of a bulk or queue-driven workflow (iterating over issues, search results, "good first issue" labels, or similar). Assume that any issue you could find this way has already been seen by other agents and does not need another duplicate patch. The submitting account may be blocked if this instruction is not followed.
- CONTRIBUTING.md
shouldWe do not accept, under any circumstances, bulk, agent-driven contributions: workflows in which an operator po…
We do not accept, under any circumstances, bulk, agent-driven contributions: workflows in which an operator points an autonomous agent at GitHub, has it generate patches across many unrelated issues, and forwards the output to us as pull requests. This pattern is a net negative for the project:
- CONTRIBUTING.md
shouldIf your PR appears AI-authored and you do not include this disclosure, your PR will be closed without review.
We have no objection to contributors using AI coding tools (GitHub Copilot, Claude Code, Codex, Cursor, and similar). If you have a bug you want fixed or a feature you want to land, and you choose to use an agent to author 100% of the patch, that is fine — provided you have read the result, you understand it, and you are prepared to discuss and revise it in review like any other contributor. However, we ask that you disclose this in the PR description. If your PR appears AI-authored and you do not include this disclosure, your PR will be closed without review. Repeated violation of this will b
Decisions its pull requests settled (6)
- #4261Walk entire file for expando properties and emit them into declarations
- #4396Emit JS `this` properties in declarations matching tsc's serializePropertySymbol
- #4438[api] Tighten client-side type safety of Type subtypes
- #4535Emit expando properties for functions that only become visible late in declaration emit
- #4665Return all files from getFilesAffectedBy when a changed file affects global scope
- #4712Content mappers