V
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 10/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- git
- Domain
- documentation
Research direction
Start by identifying what commit 79cffab82f810da04d66c903ce4134fa502e7099 refers to in the repository history. The issue names no target file, test, or requested change, so the completed result cannot be defined from the issue alone.
Written by the indexing model from the issue text.
Description
79cffab82f810da04d66c903ce4134fa502e7099
- Dominant language
- HTML
- Stars
- 5.1k
- Forks
- 4.5k
- 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 github/training-kit
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
github/training-kit#1163 · 1 comment · 1 reaction ·
-
test issue Open
Difficulty 5/5 Over a week Newbie friendliness 1/100
github/training-kit#1196 ·
-
A Open
Difficulty 5/5 Over a week Newbie friendliness 10/100
github/training-kit#1189 ·
-
Q Open
Difficulty 5/5 Over a week Newbie friendliness 10/100
github/training-kit#1188 ·
-
Difficulty 5/5 Over a week Newbie friendliness 1/100
github/training-kit#1187 ·
All issues in github/training-kit
Similar issues
-
sync-en
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
agilepathway/label-checker#640 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
BasedHardware/omi#15662 · 1 comment ·
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100