CRAN Status Check (create only one issue)

[bms63]

IS there a way to only have this fire off when a new and unique error is detected? If it is the same error on CRAN for the same flavor then we don't need additional issues created.

For example, there is something wrong with the purrr package on CRAN for windows flavor and they are working on a fix, but due to the holiday break they haven't gotten to it yet. However, our CRAN Status Checker (which is awesome) has created quite a few issues over the last two weeks.

tidyverse/purrr#1017

[dgrassellyb]

If CRAN status table can be customized (the flag column) (not sure about this) could we use the last commit ID as an unique identifier for the last deployed package (and add it on the flag column) ? and then avoid duplicated issues if it concerns the same commit ID

[bms63]

I believe that we don't have access to that table. We could we set up a Database on our pharmaverse-aws server that stores this table information with the date/commit id and then the CI action cross checks it back one date/commit id?

Also, not entirely sure how often they run these flavors.

[cicdguy]

Marking this as complete 🎉