<h1 align="center">
<a href="https://prompts.chat">
Close Stale Issues will:
Sign in to like and favorite skills
Close Stale Issues will:
stale label on issues after 90 days of inactivity.stale label after 14 further days of inactivity.stale label to be removed.include: - component: gitlab.com/tickett/components/close-stale-issues/close-stale-issues@main inputs: api_token: $REPORTER_API_TOKEN days_until_stale: 60 days_until_close: 7 dry_run: true group_id: '9970' job_suffix: ':dry-run' label: inactive
api_tokenGitLab API token.
The API token needs the
api scope to be able to retreive and update issues.
closed_messageMessage to announce when an issue is closed.
To enter a multi-line message, use the following format:
closed_message: > This is a message. This will render on the same line.\n\n This will render a new paragraph.
\n\n to start a new paragraph.days_until_closeNumber of days after labelling as stale before closing issues.
days_until_staleNumber of days inactivity before labelling issues as stale.
debugPrint debug information.
dry_runPerform a dry run.
An
api_token with only read_api scope can be used when performing a dry run.
enableEnable the job.
This allows configuring the job not to run in certain scenarios.
group_idGroup id or path to triage.
When using an id, but sure to enclose it in quotes.
host_urlThe base URL of the GitLab instance (including protocol and port).
job_suffixA suffix to add to the job name.
This is only needed if you are including this component multiple times.
labelThe label used to identify stale issues.
project_idProject id or path to triage.
When using an id, but sure to enclose it in quotes.
stageThe stage in which to run the job.
stale_messageMessage to announce when an issue is marked as stale.
To enter a multi-line message, use the following format:
closed_message: > This is a message. This will render on the same line.\n\n This will render a new paragraph.
\n\n to start a new paragraph.