github-profile-trophy
github-profile-trophy copied to clipboard
ryo-ma
🏆Looking for new trophy types
If you have any ideas please let us know. The target of aggregation is preferable to be able to obtain it using GitHub API.
A couple of ideas (maybe some are implemented already):
- Look at emoji usage (amount, variance, types used)
- Look at activity (streaks and such)
- Look at collaboration (working on own repos, collaborating with whom)
- Look at organizations (maybe there are some metrics there)
- Look at amount of code, changes (some of these may have to be derived)
It's possible some are hard to pull off and may be missing from the API but I hope that gives you some ideas.
Memo:
- All S rank over
- Event trophy: A repository of Christmas name is created at 2020 December 25. etc..
- Joined to GitHub on 2020
Would it be possible to integrate with something to show previous interaction with / completion of Hacktoberfest? The 'cheat' way to do it would just to confirm weather not 4 PRs were done during October of any given year rather than checking with something potentially interacting with a 3rd party api
@ryo-ma Hey i have a small request if it possible then please add this tokyonight theme in your repo
tokyonight: { title_color: "70a5fd", icon_color: "bf91f3", text_color: "38bdae", bg_color: "1a1b27", }
- Look at stars of all repositories (amount)
- Look at contributors of all repositories (amount)
- Look at forks of all repositories (amount)
Look at number of repositories contributed to
Similar to https://github.com/anuraghazra/github-readme-stats last parameter (Contributed to)
@qoomon I am suspending about adding normal trophies. But I want to add secret trophies.
Like this. https://github.com/ryo-ma/github-profile-trophy/issues/10#issuecomment-690842129
how do you get that multilanguage trophy, I saw it on your @ryo-ma page, but it doesn't show on mine?
@Koushikphy How to get the trophy is a secret. Because it is a secret rank. But hints are here. https://github.com/ryo-ma/github-profile-trophy/blob/master/src/github_api_client.ts#L86
Ok, I get it. The multilanguage trophy has a minimum requirement of 10 languages (https://github.com/ryo-ma/github-profile-trophy/blob/master/src/trophies.ts#L106). But mine is 6.
Heya @ryo-ma ! I don't know if this is still active xD
Maybe add a secret trophy for x amount of badges/shields used?
This might encourage people to use badges more often ƪ(˘⌣˘)ʃ. A possible sort of cheaty implementation could be to scan for the amount of popular shield/badge sites on README files?
Let me know what you think!
With github sponsors being a thing now, you could add a trophy depending on the amount of money you donate each month.
With github sponsors being a thing now, you could add a trophy depending on the amount of money you donate each month.
I agree but would say this should be a secret trophy. The trophies are supposed to measure activity after all and I dislike the idea of a highly productive college student having C rank on donations because he can't afford dropping more than a few bucks a month
I agree but would say this should be a secret trophy. The trophies are supposed to measure activity after all and I dislike the idea of a highly productive college student having C rank on donations because he can't afford dropping more than a few bucks a month
As a poor college student, I completely agree
Organization collaboration:
- At least a commit a month
- For X years in any main branch of an organization
With github sponsors being a thing now, you could add a trophy depending on the amount of money you donate each month.
Also could have a trophy for number of sponsors you have and money received
What kind of information can you get through the GitHub API?
Is it possible to see, for example, how many GitHub Project sites one user has? Or how many repos one user have with Wiki or CI configured? Maybe even handle this as a percentage, for example, the percentage of the repos of the user that have a .gitignore file in it, so it is using some good practices.
Listing the ideas:
- Good repo configuration
- Number of repos with sites configured
- Number of repos with GitHub actions associated
- Number of repos with wikis
- Number of repos with CI
- Good repo best practices
- Percentage of repos with a
.gitignore - Percentage of repos with a
README.md - Percentage of repos with
tags
- Percentage of repos with a
- Check popularity of repos
- Number of repos with more than X contributors
- Number of repos with more than X forks
I disagree with your best practices take @george-gca
Much more valuable are the artifacts listed under Insights>Community Standards such as code of conduct, security policy, issue templates and pr templates.
Not all repos need a .gitignore and the use of tags depends on the release model