_Context:_ Normally, all open issues/PRs in the repository that's running this action are retrieved then all the label, assignee, milestone, etc. criteria you provide to the action are applied. Unfortunately, this limits the action to only those issues and PRs in this repository. It also prevents operating on only a subset of issues or PRs that can't be filtered by the existing action criteria. A good example of this are PRs that are in a `review:changes_requested` state. While additional filtering criteria could be added to the action, it would result in additional callbacks to GitHub which could trigger rate-limits to be applied. _Purpose:_ This option is an array of one or more standard [GitHub Issues and Pull Requests search queries] (https://docs.github.com/en/search-github/searching-on-github/searching-issues-and-pull-requests) which will be used to retrieve the set of issues/PRs to test and take action on. These queries will be used in place of the default retrieval of all open issues and PRs for the context's owner/repo. It can be used to expand or limit the set of issues and PRs operated on beyond what is retuned by the standard query. When the retrieval is complete, all the other label, assignee, milestone, etc. criteria will be applied. You may also use this option to improve performance when you have a large number of open issues or PRs but only a small subset might be eligible for action. For instance, let's say you have 1000 open issues in your repository but only those with label `auto-closable` should ever be automatically marked as stale or closed. By default, this action would retrieve all 1000 issues _and all open PRs_ and iterate over them looking for the label you specified in the `only-issues-label` parameter. If you use the `only-matching-filter` parameter with `repo:myorg/myrepo is:issue label:auto-closable` this would limit the download to just those issues you _know_ should have further criteria applied. _Syntax:_ ``` only-matching-filter: [ "<query_string>", ... ] ``` Or if there's only one query string... ``` only-matching-filter: '<query_string>' ``` _Examples:_ To operate only on the open PRs in your organization that have a review state of `changes_requested`: ``` only-matching-filter: 'org:myorg is:pr is:open review:changes_requested' ``` Since there's only one query specified, you can omit the array syntax and just specify the string directly. GitHub only allows boolean logic and grouping in a Code Searches not in Issues and Pull Requests searches so there's no way to do an "OR" operation but you can get around this to a limited degree by specifying multiple search queries in the form of a string array. Each query is run separately and the results are accumulated and duplicates removed before any further processing is done. To retrieve all of the open PRs in your organization that have a review state of `changes_requested` or a label named `submitter-action-required`, you'd use: ``` only-matching-filter: '[ "org:myorg is:pr is:open review:changes_requested", "org:myorg is:pr is:open label:submitter-action-required" ]' ``` _Notes:_ * Each query is checked to ensure it contains an `owner:`, `org:`, `user:` or `repo:` search term. If it doesn't, the search will automatically be scoped to the owner and repository in the context to prevent accidental global searches. If the request doesn't already contain an `is:open` search term, it will automatically be added as well. * If using the array form, the value of this parameter MUST be valid JSON which means using double quotes around each query string, not single quotes. Default value: '[]' Resolves: #1143
219 lines
11 KiB
YAML
219 lines
11 KiB
YAML
name: 'Close Stale Issues'
|
|
description: 'Close issues and pull requests with no recent activity'
|
|
author: 'GitHub'
|
|
inputs:
|
|
repo-token:
|
|
description: 'Token for the repository. Can be passed in using `{{ secrets.GITHUB_TOKEN }}`.'
|
|
required: false
|
|
default: ${{ github.token }}
|
|
stale-issue-message:
|
|
description: 'The message to post on the issue when tagging it. If none provided, will not mark issues stale.'
|
|
required: false
|
|
stale-pr-message:
|
|
description: 'The message to post on the pull request when tagging it. If none provided, will not mark pull requests stale.'
|
|
required: false
|
|
close-issue-message:
|
|
description: 'The message to post on the issue when closing it. If none provided, will not comment when closing an issue.'
|
|
required: false
|
|
close-pr-message:
|
|
description: 'The message to post on the pull request when closing it. If none provided, will not comment when closing a pull requests.'
|
|
required: false
|
|
days-before-stale:
|
|
description: 'The number of days old an issue or a pull request can be before marking it stale. Set to -1 to never mark issues or pull requests as stale automatically.'
|
|
required: false
|
|
default: '60'
|
|
days-before-issue-stale:
|
|
description: 'The number of days old an issue can be before marking it stale. Set to -1 to never mark issues as stale automatically. Override "days-before-stale" option regarding only the issues.'
|
|
required: false
|
|
days-before-pr-stale:
|
|
description: 'The number of days old a pull request can be before marking it stale. Set to -1 to never mark pull requests as stale automatically. Override "days-before-stale" option regarding only the pull requests.'
|
|
required: false
|
|
days-before-close:
|
|
description: 'The number of days to wait to close an issue or a pull request after it being marked stale. Set to -1 to never close stale issues or pull requests.'
|
|
required: false
|
|
default: '7'
|
|
days-before-issue-close:
|
|
description: 'The number of days to wait to close an issue after it being marked stale. Set to -1 to never close stale issues. Override "days-before-close" option regarding only the issues.'
|
|
required: false
|
|
days-before-pr-close:
|
|
description: 'The number of days to wait to close a pull request after it being marked stale. Set to -1 to never close stale pull requests. Override "days-before-close" option regarding only the pull requests.'
|
|
required: false
|
|
stale-issue-label:
|
|
description: 'The label to apply when an issue is stale.'
|
|
required: false
|
|
default: 'Stale'
|
|
close-issue-label:
|
|
description: 'The label to apply when an issue is closed.'
|
|
required: false
|
|
only-matching-filter:
|
|
description: 'Only issues/PRs matching the search filter(s) will be retrieved and tested'
|
|
default: '[]'
|
|
required: false
|
|
exempt-issue-labels:
|
|
description: 'The labels that mean an issue is exempt from being marked stale. Separate multiple labels with commas (eg. "label1,label2").'
|
|
default: ''
|
|
required: false
|
|
close-issue-reason:
|
|
description: 'The reason to use when closing an issue.'
|
|
default: 'not_planned'
|
|
required: false
|
|
stale-pr-label:
|
|
description: 'The label to apply when a pull request is stale.'
|
|
default: 'Stale'
|
|
required: false
|
|
close-pr-label:
|
|
description: 'The label to apply when a pull request is closed.'
|
|
required: false
|
|
exempt-pr-labels:
|
|
description: 'The labels that mean a pull request is exempt from being marked as stale. Separate multiple labels with commas (eg. "label1,label2").'
|
|
default: ''
|
|
required: false
|
|
exempt-milestones:
|
|
description: 'The milestones that mean an issue or a pull request is exempt from being marked as stale. Separate multiple milestones with commas (eg. "milestone1,milestone2").'
|
|
default: ''
|
|
required: false
|
|
exempt-issue-milestones:
|
|
description: 'The milestones that mean an issue is exempt from being marked as stale. Separate multiple milestones with commas (eg. "milestone1,milestone2"). Override "exempt-milestones" option regarding only the issues.'
|
|
default: ''
|
|
required: false
|
|
exempt-pr-milestones:
|
|
description: 'The milestones that mean a pull request is exempt from being marked as stale. Separate multiple milestones with commas (eg. "milestone1,milestone2"). Override "exempt-milestones" option regarding only the pull requests.'
|
|
default: ''
|
|
required: false
|
|
exempt-all-milestones:
|
|
description: 'Exempt all issues and pull requests with milestones from being marked as stale. Default to false.'
|
|
default: 'false'
|
|
required: false
|
|
exempt-all-issue-milestones:
|
|
description: 'Exempt all issues with milestones from being marked as stale. Override "exempt-all-milestones" option regarding only the issues.'
|
|
default: ''
|
|
required: false
|
|
exempt-all-pr-milestones:
|
|
description: 'Exempt all pull requests with milestones from being marked as stale. Override "exempt-all-milestones" option regarding only the pull requests.'
|
|
default: ''
|
|
required: false
|
|
only-labels:
|
|
description: 'Only issues or pull requests with all of these labels are checked if stale. Defaults to `` (disabled) and can be a comma-separated list of labels.'
|
|
default: ''
|
|
required: false
|
|
any-of-labels:
|
|
description: 'Only issues or pull requests with at least one of these labels are checked if stale. Defaults to `` (disabled) and can be a comma-separated list of labels.'
|
|
default: ''
|
|
required: false
|
|
any-of-issue-labels:
|
|
description: 'Only issues with at least one of these labels are checked if stale. Defaults to `` (disabled) and can be a comma-separated list of labels. Override "any-of-labels" option regarding only the issues.'
|
|
default: ''
|
|
required: false
|
|
any-of-pr-labels:
|
|
description: 'Only pull requests with at least one of these labels are checked if stale. Defaults to `` (disabled) and can be a comma-separated list of labels. Override "any-of-labels" option regarding only the pull requests.'
|
|
default: ''
|
|
required: false
|
|
only-issue-labels:
|
|
description: 'Only issues with all of these labels are checked if stale. Defaults to `[]` (disabled) and can be a comma-separated list of labels. Override "only-labels" option regarding only the issues.'
|
|
default: ''
|
|
required: false
|
|
only-pr-labels:
|
|
description: 'Only pull requests with all of these labels are checked if stale. Defaults to `[]` (disabled) and can be a comma-separated list of labels. Override "only-labels" option regarding only the pull requests.'
|
|
default: ''
|
|
required: false
|
|
operations-per-run:
|
|
description: 'The maximum number of operations per run, used to control rate limiting (GitHub API CRUD related).'
|
|
default: '30'
|
|
required: false
|
|
remove-stale-when-updated:
|
|
description: 'Remove stale labels from issues and pull requests when they are updated or commented on.'
|
|
default: 'true'
|
|
required: false
|
|
remove-issue-stale-when-updated:
|
|
description: 'Remove stale labels from issues when they are updated or commented on. Override "remove-stale-when-updated" option regarding only the issues.'
|
|
default: ''
|
|
required: false
|
|
remove-pr-stale-when-updated:
|
|
description: 'Remove stale labels from pull requests when they are updated or commented on. Override "remove-stale-when-updated" option regarding only the pull requests.'
|
|
default: ''
|
|
required: false
|
|
debug-only:
|
|
description: 'Run the processor in debug mode without actually performing any operations on live issues.'
|
|
default: 'false'
|
|
required: false
|
|
ascending:
|
|
description: 'The order to get issues or pull requests. Defaults to false, which is descending.'
|
|
default: 'false'
|
|
required: false
|
|
delete-branch:
|
|
description: 'Delete the git branch after closing a stale pull request.'
|
|
default: 'false'
|
|
required: false
|
|
start-date:
|
|
description: 'The date used to skip the stale action on issue/pull request created before it (ISO 8601 or RFC 2822).'
|
|
default: ''
|
|
required: false
|
|
exempt-assignees:
|
|
description: 'The assignees which exempt an issue or a pull request from being marked as stale. Separate multiple assignees with commas (eg. "user1,user2").'
|
|
default: ''
|
|
required: false
|
|
exempt-issue-assignees:
|
|
description: 'The assignees which exempt an issue from being marked as stale. Separate multiple assignees with commas (eg. "user1,user2"). Override "exempt-assignees" option regarding only the issues.'
|
|
default: ''
|
|
required: false
|
|
exempt-pr-assignees:
|
|
description: 'The assignees which exempt a pull request from being marked as stale. Separate multiple assignees with commas (eg. "user1,user2"). Override "exempt-assignees" option regarding only the pull requests.'
|
|
default: ''
|
|
required: false
|
|
exempt-all-assignees:
|
|
description: 'Exempt all issues and pull requests with assignees from being marked as stale. Default to false.'
|
|
default: 'false'
|
|
required: false
|
|
exempt-all-issue-assignees:
|
|
description: 'Exempt all issues with assignees from being marked as stale. Override "exempt-all-assignees" option regarding only the issues.'
|
|
default: ''
|
|
required: false
|
|
exempt-all-pr-assignees:
|
|
description: 'Exempt all pull requests with assignees from being marked as stale. Override "exempt-all-assignees" option regarding only the pull requests.'
|
|
default: ''
|
|
required: false
|
|
exempt-draft-pr:
|
|
description: 'Exempt draft pull requests from being marked as stale. Default to false.'
|
|
default: 'false'
|
|
required: false
|
|
enable-statistics:
|
|
description: 'Display some statistics at the end regarding the stale workflow (only when the logs are enabled).'
|
|
default: 'true'
|
|
required: false
|
|
labels-to-add-when-unstale:
|
|
description: 'A comma delimited list of labels to add when an issue or pull request becomes unstale.'
|
|
default: ''
|
|
required: false
|
|
labels-to-remove-when-stale:
|
|
description: 'A comma delimited list of labels to remove when an issue or pull request becomes stale.'
|
|
default: ''
|
|
required: false
|
|
labels-to-remove-when-unstale:
|
|
description: 'A comma delimited list of labels to remove when an issue or pull request becomes unstale.'
|
|
default: ''
|
|
required: false
|
|
ignore-updates:
|
|
description: 'Any update (update/comment) can reset the stale idle time on the issues and pull requests.'
|
|
default: 'false'
|
|
required: false
|
|
ignore-issue-updates:
|
|
description: 'Any update (update/comment) can reset the stale idle time on the issues. Override "ignore-updates" option regarding only the issues.'
|
|
default: ''
|
|
required: false
|
|
ignore-pr-updates:
|
|
description: 'Any update (update/comment) can reset the stale idle time on the pull requests. Override "ignore-updates" option regarding only the pull requests.'
|
|
default: ''
|
|
required: false
|
|
include-only-assigned:
|
|
description: 'Only the issues or the pull requests with an assignee will be marked as stale automatically.'
|
|
default: 'false'
|
|
required: false
|
|
outputs:
|
|
closed-issues-prs:
|
|
description: 'List of all closed issues and pull requests.'
|
|
staled-issues-prs:
|
|
description: 'List of all staled issues and pull requests.'
|
|
runs:
|
|
using: 'node20'
|
|
main: 'dist/index.js'
|