Is your feature request related to a problem? Please describe.
Many organizations enforce GitHub Actions policies that restrict workflows to only use actions from verified creators on the GitHub Marketplace. Since r-lib/actions are not published there, these organizations cannot use the standard R community CI/CD workflows (check-r-package, setup-r, setup-r-dependencies, etc.) without requesting individual exceptions from their GitHub Enterprise admins. This creates significant friction for us developers.
Describe the solution you'd like
You could publish the r-lib actions to the GitHub Marketplace as a verified creator. Verified creator program provides the trust signal that enterprise administrators require to allow actions org-wide.
That probably means more work for you guys, since you would need to have multiple repos and somehow sync with this one.
Describe alternatives you've considered
- Requesting individual admin exceptions for each r-lib action: Does not scale and must be repeated per organization.
- Forking and self-hosting the actions internally: Creates maintenance burden and divergence from community standards.
Additional context
This was previously requested in #333 and #92, but was closed. Enterprise security policies have become stricter, making Marketplace verification increasingly important for action adoption. The r-lib actions are the de facto standard for R package CI/CD and their absence from the Marketplace is becoming a blocker for enterprise R users.
Is your feature request related to a problem? Please describe.
Many organizations enforce GitHub Actions policies that restrict workflows to only use actions from verified creators on the GitHub Marketplace. Since r-lib/actions are not published there, these organizations cannot use the standard R community CI/CD workflows (check-r-package, setup-r, setup-r-dependencies, etc.) without requesting individual exceptions from their GitHub Enterprise admins. This creates significant friction for us developers.
Describe the solution you'd like
You could publish the r-lib actions to the GitHub Marketplace as a verified creator. Verified creator program provides the trust signal that enterprise administrators require to allow actions org-wide.
That probably means more work for you guys, since you would need to have multiple repos and somehow sync with this one.
Describe alternatives you've considered
Additional context
This was previously requested in #333 and #92, but was closed. Enterprise security policies have become stricter, making Marketplace verification increasingly important for action adoption. The r-lib actions are the de facto standard for R package CI/CD and their absence from the Marketplace is becoming a blocker for enterprise R users.