| token | Token used to authenticate with GitHub API. Default is built-in token but a personal access token may be used for organization or user projects. | no | ${{ github.token }} |
| title | Issue title, e.g. "Daily standup" | yes | — |
| body | Issue body in Markdown, e.g. # Summary **bolded text**. | no | — |
| labels | Comma delimited list of existing issue labels to be applied to new issue, e.g. "bug, ci". | no | — |
| assignees | Comma delimited list of issue assignees having write access to repo, e.g. "imjohnbo, nat".
Assigns new issue to all assignees, or if "rotateAssignees" is set, to the next single assignee whose turn it is. | no | — |
| project-type | Project type the "project" number corresponds to, e.g. user, organization, or repository project.
Organization and user projects require a GitHub App installation access token, OAuth token, or Personal Access Token.
Read more here: https://docs.github.com/en/github/managing-your-work-on-github/about-project-boards.
Defaults to "repository". | no | — |
| project | Project number (not ID or name) to add issue to, e.g. 2. | no | — |
| project-v2-path | Path of the user or organization project, e.g. "users/{username}/projects/{number}" or "orgs/{name}/projects/{number}".
Unlike Projects (classic), Projects do not support repository projects.
Token with proper scopes required in "token" field. Personal access token or GitHub App installation access token. Read more here: https://docs.github.com/en/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects#authentication. | no | — |
| column | Project column name to add issue to, e.g. To Do.
Required if "project" is set. | no | — |
| milestone | Milestone number (not ID or name) to add issue to, e.g. 2. | no | — |
| pinned | Boolean whether to pin this issue and unpin the previous issue matching ALL of the provided "labels".
Requires "labels". | no | false |
| close-previous | Boolean whether to close the most recent previous issue matching ALL of the provided "labels".
Requires "labels". | no | false |
| linked-comments | Boolean whether to write issue comments linking this issue and previous issue matching ALL of the provided "labels",
e.g. "Previous in series: #345" and "Next in series: #346".
Requires "labels". | no | false |
| linked-comments-new-issue-text | Text of the comment on the new issue that links to the previous issue.
Requires "linked-comments, labels". | no | Previous in series: #{{ previousIssueNumber }} |
| linked-comments-previous-issue-text | Text of the comment on the previous issue that links to the new issue.
Requires "linked-comments, labels". | no | Next in series: #{{ newIssueNumber }} |
| rotate-assignees | Boolean whether to round robin the provided assignees, e.g. for first responder duties.
Requires "labels", "assignees". | no | false |