Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update badge script to add champions badge #16

Open
mpadge opened this issue Feb 7, 2024 · 1 comment
Open

Update badge script to add champions badge #16

mpadge opened this issue Feb 7, 2024 · 1 comment
Assignees

Comments

@mpadge
Copy link
Contributor

mpadge commented Feb 7, 2024

@yabellini The new champions badge (#10) won't be allocated until we update the script which generates the "onboarded.json" file. This whole workflow can only assign one badge to a review thread/package, so champions will have the new champions badge but not a "normal" peer-reviewed badge. Just so you know!

Have any champions packages passed through review yet? How quickly do we need the badges assigned? (All packages still under review just get the generic https://github.com/ropensci-org/badges/blob/main/svgs/pending.svg badge.)

@mpadge mpadge self-assigned this Feb 7, 2024
@yabellini
Copy link
Member

yabellini commented Feb 7, 2024

We have reviewed packages, which is good to have the regular badge. I don't think it should be different. (I understand you can assign one)
We also have new packages developed under the Champions Program, but don't go to peer review because the project was to create the new package.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants