v2.3.0

v2.3.0 adds support for the milestone input through the Actions workflow, thanks to @bengry:

uses: JasonEtco/create-an-issue@v2
with:
  milestone: 123

It also updates a couple of dependencies. Have fun! 🎉

v2.2.0

Thanks to @lee-dohm in #35, this release adds support for outputs - this Action now sets two outputs:

number: Number of the issue that was created
url: URL of the issue that was created

This should enable you to use this Action in more complicated workflows, and use the created issue in future Actions. Have fun!

v2.1.0

v2.1.0 adds support for the assignees input, thanks to @lee-dohm's PR #34 🎉. This can be used to override the assignees of the generated issue based on logic within your Actions workflow.

v2.0.0

This release updates the action to work with GitHub Actions v2! You can read more about the new features in this blog post.

There is a breaking change with this upgrade - using a custom issue template is now done by specifying an input instead of an argument:

steps:
  - uses: JasonEtco/create-an-issue@master
    env: 
      GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
    with:
      filename: .github/some-other-template.md

v1.2.0

This release adds better error handling for when creating the issue fails. See #13 for all the details!

v1.1.5

This release adds support for comma-delimited lists for assignees and labels to better match issue templates on GitHub.com that are created from the issue template builder UI. Try it out:

# Before
labels:
  - bug
  - other

# After
labels: bug, other

Note: array lists still work fine, mostly for backwards compatibility. Using string lists is recommended to make your templates work via the UI too!

v1.1.4

This release upgrades create-an-issue to [email protected], and switches to using Toolkit.run as the entrypoint for the script.

v1.1.3

• Use GITHUB_REPOSITORY instead of context.repo() #7

v1.1.2

This release fixes a major bug that prevents this Action from actually working in the Actions runtime. See #3 for more details!

v1.1.1

Changes

• Use actions-toolkit's .arguments to get the name of the template instead of getting them from process.argv #2