| assignees | Assignees for the issue | no | — |
| body | Project column name to add issue to, e.g. To Do.
Required if "project" is set. | no | Weekly sync issue |
| close-previous | Whether to close the previous weekly issue when creating new one | — | false |
| date-string | Date string used to add the date to the title of the issue | no | this friday |
| date-string-format | The format passed to the date command | no | %m/%d/%Y |
| title | — | no | Weekly issue for week of |
| labels | Comma delimited list of existing issue labels to be applied to new issue, e.g. "bug, ci". | no | weekly-sync |
| linked-comments | Whether to link to the previous weekly issue when creating a new one | — | true |
| 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 }} |
| 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 }} |
| milestone | Milestone number (not ID or name) to add issue to, e.g. 2. | no | — |
| project | Project number (not ID or name) to add issue to, e.g. 2. | no | — |
| pinned | Whether the issue should be pinned. | no | true |
| rotate-assignees | Boolean whether to round robin the provided assignees, e.g. for first responder duties.
Requires "labels", "assignees".
default: 'false'
required: false | — | — |
| token | GitHub token | no | ${{ github.token }} |
| 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. | no | repository |