[New Project]: Add cmd-tracker and SiteForge projects
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- content
Research direction
Review PR #490 first, since the issue says it already contains the proposed project additions. Verify the repository information for cmd-tracker and SiteForge from the two linked repositories, then check how forgoodfirstissue records projects. Done means both projects are added with their stated contribution and maintenance details.
Written by the indexing model from the issue text.
Description
Is this project already existing in the app?
- I have searched the existing projects
Tell us about the project
Repository information
The repository:
- Is a social good project.
Link: Added two open-source repositories:
-
https://github.com/adithya-naik/cmd-tracker -
https://github.com/adithya-naik/SiteForge
Both repositories are actively maintained and beginner contributors can contribute through labeled issues.
- Is for a DPG (Digital Public Good)
- The project has tags in in its description denoting which SDGs it addresses. ie
sdg-1,sdg-2, etc. - The project has a contributing file.
- The project has a code of conduct file.
- The project has a license.
- Actively maintained (last updated less than 1 months ago).
Is the Project a DPG (Digital Public Good)
- Yes
- No
Does the project list which Sustainable Development Goals it addresses in its labels?
- No
- Yes
Code of Conduct
- I've read the Code of Conduct and understand my responsibilities as a member of the GitHub community
Anything else?
I have raised a PR(#490) longback and didn't recieved any response. Please Help me to add these projects to forgoodfirstissue
- Dominant language
- TypeScript
- Stars
- 245
- Forks
- 139
- Avg merge
- 1d 23m
- Merged PRs (30d)
- 1
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/forgoodfirstissue
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
github/forgoodfirstissue#557 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
github/forgoodfirstissue#556 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
github/forgoodfirstissue#550 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
github/forgoodfirstissue#565 ·
-
PJ! Open
Difficulty 5/5 Over a week Newbie friendliness 10/100
github/forgoodfirstissue#563 ·
All issues in github/forgoodfirstissue
Similar issues
-
clawsweeper:linked-pr-open clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:message-loss issue-rating: 🦞 diamond lobster maturity:stable P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#616 ·
-
ZCode 3.14.3 に対応する Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
supermomonga/zcode-acp#24 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
growthbook/growthbook#7100 ·
-
triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100