Automate and improve typespec-next checks
Open
eng
feature
- Dominant language
- TypeScript
- Stars
- 27
- Forks
- 90
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 156
Description
- Add ci check for PRs that tests against typespec-next
- Fix typespec-next build issue on Windows
This is a work item from the June Retrospective
Contributor guide
Research direction
Start by locating the existing CI configuration and the typespec-next build path, then reproduce the build issue on Windows. Done means pull requests run a typespec-next check and the typespec-next build succeeds on Windows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100