René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Inverse Command","articleBody":"👋 fellow Hubber! Love this action and its versatility.\n\nOne idea that came to mind that would be helpful would be to specify an opposite/inverse of a command that would force the `continue` output to be `'false'`. Specifically I was thinking about approval workflows that happen in issues instead of PRs. Currently, this would have to be implemented with two different `github/command` steps (one for `.approve` and one for `.deny`).\n\nAlternatively, it'd be helpful to combine them into one step:\n\n```yaml\n- name: Approve Command\n  id: approve\n  uses: github/command@vX.X.X\n  with:\n    allowed_contexts: issue\n    command: .approve\n    opposite: .deny\n```\n\nWhat do you think?\n\n_Edit:_ I just realized that I probably worded this poorly. I know that further steps that check the `continue` output would not run because commenting with `.deny` would not match the expected keyword. What would probably work better would be to have a separate output that is set when the opposite command is provided.","author":{"url":"https://github.com/ncalteen","@type":"Person","name":"ncalteen"},"datePublished":"2023-10-31T19:01:11.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/9/command/issues/9"}