Reporting Type Errors in Pull Requests
What you'll learn: How to surface TypeScript type errors directly in pull request comments and status checks so developers get immediate feedback before merging.
The Problem: Hidden Type Errors
When TypeScript runs in CI (as we set up previously with tsc --noEmit), it can fail your build — but developers often have to dig through CI logs to understand what went wrong. This creates friction: someone opens a PR, waits for CI, sees a red X, clicks through multiple pages, scrolls through logs, and then discovers they forgot to update a type annotation.
The Solution: Inline PR Feedback
Modern CI platforms and third-party tools can parse tsc output and post inline comments directly on the lines of code that contain type errors. They can also update the PR's status check with a summary, making errors visible at a glance.
How It Works
- CI runs
tsc --noEmitto type-check without emitting files - Parse the error output (TypeScript outputs errors in a structured format)
- Post comments on specific file lines via the platform's API (GitHub, GitLab, etc.)
- Update status checks with pass/fail and error count
Common Integration Approaches
GitHub Actions with reviewdog:
A popular tool that reads tsc output and creates PR review comments automatically. It understands TypeScript's error format and maps errors to file locations.
Dedicated TypeScript CI Bots:
Services like Danger.js can run custom scripts that invoke tsc, parse errors, and post formatted messages directly in PR threads.
Platform-Native Annotations:
GitHub Actions supports "annotations" that appear as inline warnings without third-party tools — you can format tsc output to match this format.
Benefits
- Immediate visibility: Developers see errors without leaving the PR page
- Faster iteration: No need to clone locally and run type-checks to understand CI failures
- Better code review: Reviewers see type issues highlighted alongside code changes
- Reduced context switching: Error location, message, and code are all in one view
Key Takeaway: Integrating type-checking results into PR comments and status checks transforms type errors from hidden CI failures into actionable, inline feedback that speeds up the review and fix cycle.