Move to next iteration
ActionsTags
(2)Automatically move issues and pull requests to the next iteration of your GitHub project with this Github Action.
on:
schedule:
# Runs "at 05:00, only on Monday" (see https://crontab.guru)
- cron: '0 5 * * 1'
jobs:
move-to-next-iteration:
name: Move to next iteration
runs-on: ubuntu-latest
steps:
- uses: blombard/move-to-next-iteration@master
with:
owner: OrgName
number: 1
token: ${{ secrets.PROJECT_PAT }}
iteration-field: Iteration
iteration: last
new-iteration: current
statuses: 'Todo,In Progress,In Review'Alternatively, you may specify excluded-statuses. In this case, all items that don’t have these statuses will be moved to the new iteration. (Note that if excluded-statuses is used, statuses will be ignored.)
on:
schedule:
# Runs "at 05:00, only on Monday" (see https://crontab.guru)
- cron: '0 5 * * 1'
jobs:
move-to-next-iteration:
name: Move to next iteration
runs-on: ubuntu-latest
steps:
- uses: blombard/move-to-next-iteration@master
with:
owner: OrgName
number: 1
token: ${{ secrets.PROJECT_PAT }}
iteration-field: Iteration
iteration: last
new-iteration: current
excluded-statuses: "Done,Won't Fix"The account name of the GitHub organization.
Project number as you see it in the URL of the project.
Personal access token or an OAuth token. the project scope is required.
The name of your iteration field.
Should be last or current.
Should be current or next.
Statuses of the issues to move to the next iteration.
excluded-statuses is provided. See below.
Statuses of the issues that should not be moved.
statuses.
This action was made possible thanks to https://github.com/gr2m/github-project.
Move to next iteration is not certified by GitHub. It is provided by a third-party and is governed by separate terms of service, privacy policy, and support documentation.