Enable automated PreFast static analysis for WIL
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 3k
- Forks
- 300
- Avg merge
- 19h 12m
- Merged PRs (30d)
- 1
Description
Filing this issue to track the following work:
Q: Can WIL on GitHub run PreFast to catch issues by itself, versus requiring WIL clients to spend time investigating PreFast bugs that originate from WIL?
A: There's a github action for Prefast: microsoft/msvc-code-analysis-action: Microsoft Visual C++ Code Analysis GitHub Action. If someone sets this up, it should probably be configured to run the same (or a subset) ruleset that's run in the OS repo so all defects can be fixed on the github side and won't show up in the OS.
Contributor guide
No contributing guide indexed for this repository
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 reviewing microsoft/msvc-code-analysis-action and the ruleset used in the OS repository. Configure WIL's GitHub workflow to run PreFast with the same or an appropriate subset of those rules, and confirm the action reports WIL defects during CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100