Fail R-CMD-check workflow on NOTEs to catch CRAN-blocking issues#65
Fail R-CMD-check workflow on NOTEs to catch CRAN-blocking issues#65
Conversation
Co-authored-by: osorensen <21175639+osorensen@users.noreply.github.com>
osorensen
left a comment
There was a problem hiding this comment.
This did not work. Here is the output from one of the tests. The others are the same.
Run r-lib/actions/check-r-package@v2
Run ## --------------------------------------------------------------------
Error: Error: object 'note' not found
Execution halted
Error: Process completed with exit code 1.
Run ## --------------------------------------------------------------------
Show testthat output
Run actions/upload-artifact@v4
Warning: No files were found with the provided path: /Users/runner/work/BayesMallowsSMC2/BayesMallowsSMC2/check. No artifacts will be uploaded.
Run actions/upload-artifact@v4
No files were found with the provided path: /Users/runner/work/BayesMallowsSMC2/BayesMallowsSMC2/check/**/tests*/testthat/_snaps. No artifacts will be uploaded.
Co-authored-by: osorensen <21175639+osorensen@users.noreply.github.com>
Fixed in f8a7167. The issue was that |
Plan: Update GitHub Actions Workflow for CRAN NOTEs
Changes Made
error-on: noteparameter to thecheck-r-packageaction in.github/workflows/R-CMD-check.yamlerror-on: 'note'toerror-on: note(unquoted) to prevent R evaluation errorFix Applied
The initial implementation used quoted string
'note'which caused GitHub Actions to attempt R evaluation, resulting in "Error: object 'note' not found". The correct syntax is an unquoted valuenote.Security Summary
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.