The right way
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 4k
- Forks
- 159
- PR merge metrics
- No merged PRs in 30d
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!˜
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.
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.
Assessment
- Tech stack
- javascript, react
- Domain
- developer-experience, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100