Use consistent code formatting
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
No file, linter, or test is named. Start by inspecting the repository structure and existing build or development configuration to identify where formatting checks belong. The issue is done when a selected linter configuration consistently enforces the project's C++ formatting, but the required style and validation command still need clarification.
Written by the indexing model from the issue text.
Description
Set up a linter config to enforce this.
- Dominant language
- Ruby
- Stars
- 31
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
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.
More from UCL/research-computing-with-cpp
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
UCL/research-computing-with-cpp#154 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Refactor Week 1Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in UCL/research-computing-with-cpp
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
simp/pupmod-simp-stunnel#173 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
TheOdinProject/curriculum#31444 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100