Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: issue-ops/parser
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v2
Choose a base ref
...
head repository: issue-ops/parser
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v3.0.0
Choose a head ref
  • 4 commits
  • 31 files changed
  • 1 contributor

Commits on Aug 29, 2024

  1. Disable linting rule

    @ncalteen
    ncalteen committed Aug 29, 2024
    Configuration menu
    Copy the full SHA
    52c2c84 View commit details
    Browse the repository at this point in the history

  2. Ignore .env (@github/local-action testing)

    @ncalteen
    ncalteen committed Aug 29, 2024
    Configuration menu
    Copy the full SHA
    dec1804 View commit details
    Browse the repository at this point in the history

  3. Default to template field ID for parsed issue body key 

    By default, when an issue body is parsed, the action will now attempt to match the header in the issue body markdown with the label field of the issue template. If found, it will check if an ID is present for that field. If present, the ID will be used for the property key. Otherwise, the action reverts to the original behavior (slugifying the field label).

E.g. If the field looks like this in the template:

```yaml
  - type: input
    id: name
    attributes:
      label: The Name of the Thing
      description: The name of the thing you want to create.
      placeholder: this-is-the-thing
    validations:
      required: true
```

Then the parsed issue body will loo like this:

```json
{
  "name": "Whatever the user-provided value is"
}
```

Otherwise, if the field looks like this in the template

```yaml
  - type: input
    attributes:
      label: The Name of the Thing
      description: The name of the thing you want to create.
      placeholder: this-is-the-thing
    validations:
      required: true
```

Then the parsed issue body JSON will look like:

```json
{
  "the_name_of_the_thing": "Whatever the user-provided value is"
}
```
    @ncalteen
    ncalteen committed Aug 29, 2024
    Configuration menu
    Copy the full SHA
    602b9f7 View commit details
    Browse the repository at this point in the history

  4. Merge pull request #73 from issue-ops/ncalteen/72 

    Default to template field ID for parsed issue body key
    @ncalteen
    ncalteen authored Aug 29, 2024
    Configuration menu
    Copy the full SHA
    b573c08 View commit details
    Browse the repository at this point in the history
Loading