Note
Project workflow automations must be enabled by an enterprise owner in the enterprise settings page for policies for projects. For more information, see "Enforcing policies for projects in your enterprise."
About automatically archiving items
You can configure your project's built-in workflows to automatically archive items. Archiving items will help you stay below the limit of 1,200 items in each project.
The auto-archive workflow supports a subset of filters. You can use the following filters when configuring your workflow.
| Qualifier | Possible values |
|---|---|
is | open, closed, merged, draft, issue, pr |
reason | completed, reopened, "not planned" |
updated | <@today-14d (the last 14 days), <@today-3w (the last 3 weeks), <@today-1m (the last month) |
GitHub Enterprise Server marks an issue or pull request as updated when it is:
- Created
- Reopened
- Edited
- Commented
- Labeled
- Assignees are updated
- Milestones are updated
- Transferred to another repository
Additionally, items are also marked as updated when field values in your project are changed.
When you enable automatic archiving for issues or pull requests, items in your project that already meet your criteria will also be archived. There may be some delay in archiving large numbers of items that already meet the criteria.
Projects also have a limit on the number of archived items they can contain. Your project can contain up to 10,000 archived items. For more information on permanently deleting items, see Archiving items from your project.
Configuring automatic archiving in your project
-
Navigate to your project.
-
In the top-right, click to open the menu.
-
In the menu, click Workflows.
-
In the "Default workflows" list, click Auto-archive items.
-
In the top right, click Edit.
-
In the "Filters" field, type the filter criteria you want to use to automatically archive items. You can only use the
is,reason, andupdatedfilters. -
To save your changes and enable the workflow, click Save and turn on workflow.
