The person with the most amount of starred projects?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
The issue names no files, tests, or entry points. Start by reviewing the repository's Python ranking functionality and how it obtains GitHub data, then clarify the leaderboard's scope, data source, and completion criteria before implementation.
Written by the indexing model from the issue text.
Description
I got 1.8 k projects starred* and I currently used a script to download all of the names to save them in txt file
The reason I am asking this is because, I am not sure if this idea is beyond the scope of the project but I am merely putting this out as an discussion as I am interested to know what people exactly are star-addicts like me. My reasoning to stars is to show my support or as bookmark, If I go to a page and I find it remotely interesting I usually star although I feel like there are probably around 100-200 stars that I star simply because no one else has starred and I want to show my support in a way because I feel like its a way of saying thank you for them for just giving to open source in a way and also as a bookmark to those things as well.
Are there any other people like me, I have come to a point where I am unable to find the projects in my stars :) and I know that I saw some projects which can do unique things but forget the name and my star list becomes a better source of truth than even search engines in my case
I am sure that there must be some people who star a lot of projects in a similar way and as I said earlier, it would be a good leaderboard idea/ a way for us people to connect perhaps too :)
Is there any github api which can show something like this, I presume not and I don't really know about how to proceed and so I came here, its just
- Dominant language
- Python
- Stars
- 12.2k
- Forks
- 703
- 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 EvanLi/Github-Ranking
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
EvanLi/Github-Ranking#59 · 2 reactions ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
EvanLi/Github-Ranking#61 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
EvanLi/Github-Ranking#51 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
EvanLi/Github-Ranking#50 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
EvanLi/Github-Ranking#48 · 1 reaction ·
All issues in EvanLi/Github-Ranking
Similar issues
-
sponsored
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Diaoul/subliminal#1382 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
triage/confirmed
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
agentscope-ai/agentscope#2775 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100