-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add action for useful PR commands #16
Comments
yes it's possible. yes I don't like 😄 |
Would still be nice to have it in this repo so that maintainers can optionally include it (the ones that want it) |
Note that there are many ways to trigger a workflow. I always felt like the "\style" comment was a bit hacky. Could also be something like labelling a PR with a "auto-style" label or something. |
¯_(ツ)_/¯ i'm not really picky about how to trigger it tbh. Happy if you want to do it a custom way via labels, but I wolud prefer to just leave it the way r-lib does it so we don't unnecessarily add extra maintenance burden on ourselves if we don't have to (even if it's a tiny burden lol) |
NB: since I'm expecting everything in the on:
workflow_call: anything that's invoked on comment will need to have a workflow file in the content repo:
|
It is possible to ask GitHub to run common commands like
roxygen2::roxygenise()
to document a package, orstyler::style_pkg()
directly from GitHub. It will then commit the results to the PR. You do so by typing\style
or\document
as a comment on the GH PR.I know @cjyetman doesn't particularly like things that make commits for him, but these are entirely opt-in (meaning people that want to use them can use them, and people that don't don't need to).
See here: https://github.com/RMI-PACTA/r2dii.data/blob/main/.github/workflows/pr-commands.yaml
The text was updated successfully, but these errors were encountered: