Add some form of CI for Windows
Open
- Dominant language
- Assembly
- Stars
- 1.7k
- Forks
- 223
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 7
Description
Just as the title says. There should be continuous testing on Windows x86_64 and arm64 so that releases don't just break with a BoringSSL bump, etc. Even just a smoke test would be extraordinarily helpful.
Contributor guide
Research direction
No specific files or tests are named. Start by locating the repository's existing CI configuration and supported-platform setup, then determine how Windows x86_64 and arm64 can run at least a smoke test. Done means continuous Windows coverage is established for both architectures and can catch release-breaking changes such as BoringSSL bumps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- ci-cd, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100