microsoft / microsoft/TypeScript
Provide passive `extendedDiagnostics` feedback on PRs
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
@amcasey had suggested that we provide performance feedback for changes, similar to what we do on DefinitelyTyped. This could be a part of the standard CI process, where @typescript-bot provides the output of tsc -p src/compiler as a comment and compares it against a baseline.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining the standard CI configuration and how DefinitelyTyped provides performance feedback, then run tsc -p src/compiler to inspect the extended diagnostics output. Trace how @typescript-bot currently comments on pull requests and determine how a baseline comparison should be represented; done means automated PR feedback with the diagnostics and comparison.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ci-cd, performance, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100