discord roles for contributors
maybe something like this:
- New Contributor
- Contributor
- Try Hard
- Hero
- King
- Legend
42 Replies
Weekly Role Thresholds:
====================
šš: 100+ points
š: 75+ points
āāā: 50+ points
āā: 30+ points
ā: 10+ points
All-Time Role Thresholds:
=====================
Legend: 100+ points
King: 75+ points
Hero: 50+ points
Try Hard: 30+ points
Contributor: 10+ points
New Contributor: 3+ points
am trying out with clg now
will see tmrw about discord integration
I like King @ansh.grover š
@om me too, due to college not in my best form.š but yeah soon, i will
If anybody knows about discord can do these
I think Seve have to create roles beforehand
then bot will add/remove them every wed
The main question is how can we find discord profile by GitHub username?
Ah yea we do need thatā¦
Is this workflow alright if I work in this issue?
User ā Go to sync page on contribution tracker website ā Login with Discord oauth with connections info ā Data sent to backend private api ā Save githubusername with corresponding discord username in users.json ā Commits newly users.json on Repo Directly/Database ā Workflow runs everyweek initiates script ā Script processes contribution scores of last week ā Matches users.json ā Update discord roles by discord authorised custom guild bot ā ā
@Seve @DOPĪ£
/register github:yourgithubusername we can create a Discord bot command for users to register their GitHub username/register GitHub:ansh.grover
What if I chose you username
@DOPĪ£ it has some verification system
yeah
The only way to verify GitHub account is by discord connections
And for that we need oauth
I like the idea of /register to keep it simple
We can use oauth to verify people if we get bigger
@Seve https://github.com/tscircuit/jlcsearch/issues/27 can we move this issue to the the right repo as you said in meeting it is in wrong repo
GitHub
Make sure internal links use the correct http (local) or https (pro...
Damaging our seo score /bounty $5
/register could also just open a link to a github pr to the contribution tracker so that we can go thru regular github process
Its in the right repo
For auth
we have to create an express app and use that in react app
Here the issue is we have to run bot all the time
I was thinking of running just before the meet or after every wed
Where possible we should deploy to vercel, or have a github action. I think /register could hit a vercel endpoint
Express is not serverless so kind of annoying to run
Yeah have to think something else
For now let's just keep a json file which maps usernames from GitHub to discord
I will try to create a pr tonight
In uni ...
@DOPĪ£ will continue this
maybe my potato research not help
Is this final?
Yeah
@Seve button is for if someone wants to add there discord account with corresponding GitHub username
It's redirects to discord oauth where on server user discord and GitHub connection is matched and automatically creats pr to add user discord id & GitHub username to codebase
Do we need to remove it?
Like this
Yea lets put it at the bottom and rename it to something like āConnect my discord account to contributionsā, also im not sure we need all the oauth- they could just type in their discord name and their github name? Im glad you understand how all the oauth works but auth is annoying to maintain and has a bit of a security risk
Umm what if somebody for trolling add your user name others username and random discord or any typos? Do we need to check one by one?
It would be a good day when we have too many requests, no need to scale too early
what if one mod does that [internally]
like its job of mod to do community stuff isnt it
also cant we access github from discord account
maybe check this aspect too
like I have connected
So I'm removing ui changes, only workflow and script, is everything else alright for merge?
Ummm idk that would be ease for me I don't need to fix any issues on ui, idk
Should we still have a button at the bottom so people know what to do? (How to connect?)
Button and bottom, redirecting to readme saying how to link discord and GitHub? Should I do it?
Ya sg
š« will try to do if my laptop wakes, Thanks for review
For sure, code looks good but fwiw we should only start counting all time roles starting this week, some weeks in the past have inflated data
@Seve so this means if previous someone had worked hard as their ass off it does not mean to you anything just askingš
Ansh we dont make money right now
So the value of everything everyone has done is $0 in the market
We have a long way to go š
It would get latest file data only, like if you merge rn, and in next run suppose on Wednesday, it would take latest week data ie this week's data
Ps - don't merged rn I'll wix asap as soon as ass wakes up
Thats why I am confident in my code
yes, but then what is the role of this thing if it does not mean anything like i see this as new contributor who comes here judge with this roles.
you are right, but then let take example of abse he also called here new contributor from this week because from few previous weeks he is merging like 2 or pr something
so our future work does not counted here, thats right.
no we have plan on getting crowns but the situation currently not as before as you think we are doing work and will always do as before but i think you misunderstood what i mean to say? @Seve
leave it, thanks.!!
Actually the truth of it is ive hired a lot of people in the past and every time theyve gotten an inflated title too soon it has been a huge problem (think: hiring vp of engineering), since i know the data in the past is broken and can point out examples of inflated metrics, i would be doing the same thing.
We have a long journey ahead, so i dont think it makes sense to bias the system (it used to have a 10 day bug!!! That is major inflation!!) plus I would like to start at 0 too and see if i can get the Legend status again š
@Seve ok make sense.!!!
@Seve but only want to point out one thing people can inflate the data you are purely right but not total no of merged prs in previous weeks just want to say. not going to say anything word again after this.
