Number of stars in the Starstruck badge seems to be wrong

[realamirhe]

It seems to be hardcoded "⭐️ 16 stars"

https://github.com/realamirhe?tab=achievements&achievement=starstruck
https://github.com/realamirhe/immer-store has 56 starts

https://github.com/aaronchall?tab=achievements&achievement=starstruck
https://github.com/aaronchall/pythontrainer has 47 stars

[shaido987]

Yes, it's on purpose. The achievement is awarded when you have a created repository with >= 16 stars. When you reach 128 stars the bronze tier is unlocked, then silver at 512 and gold at 4096. You can see an example of how it looks with all unlocked here: https://github.com/torvalds?achievement=starstruck&tab=achievements

Note that it still says 16, 128, 512, and 4096 stars even though the repository has more.

[realamirhe]

Thanks for your response :)

[dandv]

I was also confused by this. The count jumps from 16 to 128, even though I have a repo with 40 stars.

[dandv]

I will mutually add your repository to favorites, here is mine: https://github.com/Karkatov/TaskManager

This doesn't feel ethical. @github-staff

[VictorHugoAguilar]

Hello all,
for get starstruck need to reach 10 star. If u want u can put star on my readme repository, I will do the same for you.

https://github.com/VictorHugoAguilar/ticketing-microservices-node-nextjs-react

[dandv]

Hello all, for get starstruck need to reach 10 star. If u want u can put star on my readme repository, I will do the same for you.

@github-staff, is it OK to solicit likes for likes?

[tjcchen]

@dandv @github-staff Yeah, I think this is inappropriate too.

[dripton-art]

I'm wondering if I put stars on other people's repositories, do I also earn the Starstruck badge?
@github-staff

[shaido987]

No, it's the number of stars on your own repository.

[dripton-art]

ohhh thanks alot

[davidlucus80]

That error usually means R is using an old or invalid GitHub token. Quick fix: run gitcreds::gitcreds_delete(), then try remotes::install_github("johnbaums/rmaxent") again. If you want a permanent fix, create a new personal access token on GitHub, set it with gitcreds::gitcreds_set(), then the install will work without the 401.