v1.0.4

1.0.4 (2021-09-12)

Bug Fixes

• semantic-release setup (21b7212)

v1.0.3

1.0.3 (2021-09-12)

Bug Fixes

• do not publish node_modules folder (4bf5102)

v1.0.2

1.0.2 (2021-09-12)

Bug Fixes

• semantic-release setup (#18) (44d26c5)

v1.0.1

1.0.1 (2021-09-12)

Bug Fixes

• multi paragraphs parsing (#15) (e78326b)

v1.0.0

GitHub Issue Parser

Use this action to convert issues into a unified JSON structure.

Setup

- uses: stefanbuck/github-issue-parser@main
  id: issue-parser
  with:
    template-path: .github/ISSUE_TEMPLATE/bug-report.yml

- run: echo ${{ toJSON(steps.issue-parser.outputs.jsonString) }} > bug-details.json

template-path is optional and meant to be used with Issue Forms.

Example

Given an issue form

name: Bug
description: Something is broken

title: "Order Pizza"

body:
  - type: input
    id: contact
    attributes:
      label: Your contact details
    validations:
      required: true

  - type: input
    id: what_happened
    attributes:
      label: What happened?
    validations:
      required: true

  - type: input
    id: version
    attributes:
      label: Version
    validations:
      required: true

  - type: input
    id: browsers
    attributes:
      label: What browsers are you seeing the problem on?
    validations:
      required: true

  - type: checkboxes
    attributes:
      label: What else?
      options:
        - label: Never give up
        - label: Hot Dog is a Sandwich

And an issue body

### Your contact details

me@me.com

### What happened?

A bug happened!

### Version

1.0.0

### What browsers are you seeing the problem on?

Chrome, Safari

### What else?

- [x] Never give up
- [ ] Hot Dog is a Sandwich

The actions output will be

{
  "contact": "me@me.com",
  "what_happened": "A bug happened!",
  "version": "1.0.0",
  "browsers": "Chrome, Safari",
  "never_give_up": true,
  "hot_dog_is_a_sandwich": false
}