[Activity] Run C++ Specific Validation
- Dominant language
- C#
- Stars
- 135
- Forks
- 260
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 144
Description
### 🧩 Name of the Activity
C++ Specific Validation
### 🎯 Goal of this Activity
Run C++ specific validation
### 🌟 Champion Scenarios
_No response_
### 🔧 How is this Activity Done Today?
_No response_
### 🛠️ Tools Needed to Support This Activity
Add the C++ specific validation checks that are known pain points for users and/or would block release if they fail.
This includes currently the following checks, Implement the following that are applicable for your language and update this issue with why each one is being implemented or not:
- [ ] DependencyCheck
- [ ] Lint
- [ ] Format
- [ ] UpdateSnippets
- [ ] ValidateSamples -> building samples (if necessary) and ensuring format etc runs on them
- [ ] VerifyReadme
- [ ] VerifyChangelog
- [ ] Cspell
Contributor guide
Research direction
Start by reviewing the repository's existing validation tooling and the C++ checks listed in this issue. Determine which checks apply, identify their entry points, and document or implement each applicable check; done means the selected validations run successfully and the issue records why others are excluded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing-qa, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100