CI Auto-Update Job
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- build-system, ci-cd
Research direction
No files or tests are named; start by inspecting the repository's existing CI configuration and build entry points. Define the weekly update flow for the libcxx and libcxxabi mirrors, verify the build, and confirm that commits occur only after a successful check.
Written by the indexing model from the issue text.
Description
Create a CI job which weekly tries to udpate the libcxx and libcxxabi mirrors, checks the build, and then commits them if it's all OK.
- Dominant language
- C++
- Stars
- 99
- Forks
- 19
- 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 embeddedartistry/libcpp
-
question
Difficulty 5/5 Over a week Newbie friendliness 25/100
embeddedartistry/libcpp#54 · 4 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
embeddedartistry/libcpp#50 · 8 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
embeddedartistry/libcpp#43 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
embeddedartistry/libcpp#38 ·
-
Build System
Difficulty 4/5 3-5 days Newbie friendliness 35/100
embeddedartistry/libcpp#29 ·
All issues in embeddedartistry/libcpp
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
objectionary/eo-graphs#74 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 88/100
QuantStack/git2cpp#187 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100