How do we do this?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- cli, documentation
Research direction
The issue names no file, test, or entry point. Start by reviewing the C++ command-line skeleton and its existing project context, then determine what workflow the author is asking about; done means a maintainer provides the requested brief explanation.
Written by the indexing model from the issue text.
Description
I'm not totally sure how this works - would ❤️ some brief insight from @springmeyer and @camilleanne!
- Dominant language
- Makefile
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Contributor 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 mapbox/cpp-cli-skel
-
Status of project Open
Difficulty 5/5 Over a week Newbie friendliness 20/100
mapbox/cpp-cli-skel#4 · 2 comments ·
-
add cmake file Open
Difficulty 3/5 1-2 days Newbie friendliness 40/100
mapbox/cpp-cli-skel#3 ·
All issues in mapbox/cpp-cli-skel
Similar issues
-
triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
app bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
kovidgoyal/kitty#10516 ·