Max Held

thanks so much for the thoughtful suggestions @mllg and @nutterb. @mllg I agree with @nutterb; I haven't encountered this often, thought it sometimes happens when I have functions with lots...

one more application of looping assertions comes to mind, though it's slightly different: When users provide a >1d vector or dataframe as an argument, it can sometimes be helpful to...

(this was partly inspired by @hadley's [error message style guide](http://style.tidyverse.org/error-messages.html))

perhaps, a somewhat off-the-cuff suggestion, after all (of the interface): ``` check_consistency(x, # object 1, y, # object 2, # all of the following conditions must be read as: x...

+1

also, this fails silently.

absolutely, that is correct, r-lib/actions is the place to go. I'm still figuring out what to do with *this* package (ghactions), or whether to deprecate it entirely. r-lib/actions includes yaml-templates...

thanks for the recommendation; I *do* have some actions on the marketplace, though the current iteration of this package includes no actions, but just writes out variants of existing actions.

Just emailed support: > Hi octocats, > I just noticed that the reame on GitHub Marketplace listings for actions is whatever is at my master HEAD.  > My expectation was...

I'm not really too sure what that would add over just going through the logs, but I guess it could be done.