Formatting and code style
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
- Add a .clang-format file that applies our style conventions.
- Add a GitLab CI job that requires
clang-formatandblackto find no needed changes for C++ and Python code, respectively. - Consider adding rules for clang-tidy to check naming conventions, as well. (
readability-identifier-naming) - Consider using
pre-committo apply formatting fixes automatically.
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 with the .clang-format target and the GitLab CI job described in the checklist, then review the proposed clang-tidy naming rule and pre-commit option. Clarify which checklist items are in scope; done means the agreed formatting and style checks require no needed changes for the C++ and Python code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, gitlab, python
- Domain
- build-system, ci-cd, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100