You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@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!
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.
@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.)
The text was updated successfully, but these errors were encountered: