peter-murray / issue-body-parser-action Goto Github PK

I am using this action in a workflow that is triggered on issue opened and issue_comment created. Sometimes issues do not have the payload this action is looking for, which is expected. The workflow runs regardless, which is also expected. However, the workflow fails because the payload is not found in the issue body. This failure is not ideal. It would be great if there were an option that caused the action to not fail if the payload is missing. Perhaps this option could also set a default value for the payload if it is not found so that downstream actions can check for this default value and behave accordingly.

dsgadgadgadgadgqegq ergwergwergw

Hi,

Thanks a lot for creating this action, it's very helpful in the workflow we are designing.
One question/ request, when running your action we get a warning about using a deprecated version of node (node 16) while the most recent version to be used is node 20. Is there any chance to update this module to use node 20? See the screenshot for reference.

I have had a quick look and noticed the following in action.yml:

runs:
  using: node16
  main: dist/index.js

It might be as simple as changing this to use node20 instead of node16, but not really certain.

I would definitely appreciate some assistance in that regard. Thanks!

nada

test for the parser

This is a JSON payload

{
  "name": "payload",
  "version": "1.0.0"
}

A standard JSON code block

{
  "name": "IS NOT PAYLOAD"
}

Some YAML encoded data

yaml_payload:
  name: A YAML payload
  version: 2.0.0