The right way
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
- javascript, react
- Domain
- developer-experience, documentation
Research direction
Start by reviewing the repository README and the PR referenced in the issue to understand the current contribution context. A complete outcome would be a concrete, agreed-upon next contribution and best-practice guidance; the issue does not identify a file, test, or specific change.
Written by the indexing model from the issue text.
Description
I would like to know if my PR is following the best practices, and what should I do as of right now to continue contributing with the project. Iam new to programming and sometimes I move a little bit too fast. My goal is that EVERYONE with the same problem/pain as us can use the software as EASILY as possible. I am starting with REACT and JS, you can look at my READ.me. But if possible and with time I would like to transform it into a .exe or something as public as possible so everyone in the world can organize themselves better!
Thanks!˜
- Dominant language
- Shell
- Stars
- 4k
- Forks
- 159
- PR merge metrics
- No merged PRs in 30d
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.
More from tobi/try
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2218 ·
-
docs(agents): strengthen the no-backslash-escaped-backticks rule with an issue-creation example Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
chore
Difficulty 1/5 Under an hour Newbie friendliness 91/100
alunduil/alunduil-chezmoi#792 ·