jellyfin/.github/stale.yml

# Number of days of inactivity before an issue becomes stale
daysUntilStale: 120
# Number of days of inactivity before a stale issue is closed
daysUntilClose: 21
# Issues with these labels will never be considered stale
exemptLabels:
  - regression
  - security
  - dotnet-3.0-future
  - roadmap
  - future
  - feature
  - enhancement
  - confirmed
# Label to use when marking an issue as stale
staleLabel: stale
# Comment to post when marking an issue as stale. Set to `false` to disable
markComment: >
  This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.

  If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or nightlies, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.

  This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on [Matrix or Social Media](https://docs.jellyfin.org/general/getting-help.html).
# Comment to post when closing a stale issue. Set to `false` to disable
closeComment: false

# Disable automatic closing of pull requests
pulls:
  daysUntilClose: false
Add Stale app configuration starting point Link: https://github.com/apps/stale 5 years ago			`# Number of days of inactivity before an issue becomes stale`
Update stalebot timings and message 1. Bump up the timings, since the project releases have slowed down a fair bit. 120 days stale with 21 days for a response still gets us the desired effect while loosening the timeline for issue submitters. 2. Revamp the wording to better explain what the author (or others) need to do, and why this bot exists. 5 years ago			`daysUntilStale: 120`
Add Stale app configuration starting point Link: https://github.com/apps/stale 5 years ago			`# Number of days of inactivity before a stale issue is closed`
Update stalebot timings and message 1. Bump up the timings, since the project releases have slowed down a fair bit. 120 days stale with 21 days for a response still gets us the desired effect while loosening the timeline for issue submitters. 2. Revamp the wording to better explain what the author (or others) need to do, and why this bot exists. 5 years ago			`daysUntilClose: 21`
Add Stale app configuration starting point Link: https://github.com/apps/stale 5 years ago			`# Issues with these labels will never be considered stale`
			`exemptLabels:`
			`- regression`
			`- security`
			`- dotnet-3.0-future`
			`- roadmap`
			`- future`
Update message for stale issues and also ignore feature and enhancement labels 5 years ago			`- feature`
			`- enhancement`
Add an exemption for the confirmed label Adds an exemption we can use to keep issues open when they are confirmed/real 5 years ago			`- confirmed`
Add Stale app configuration starting point Link: https://github.com/apps/stale 5 years ago			`# Label to use when marking an issue as stale`
			`staleLabel: stale`
			# Comment to post when marking an issue as stale. Set to `false` to disable
			`markComment: >`
Update stalebot timings and message 1. Bump up the timings, since the project releases have slowed down a fair bit. 120 days stale with 21 days for a response still gets us the desired effect while loosening the timeline for issue submitters. 2. Revamp the wording to better explain what the author (or others) need to do, and why this bot exists. 5 years ago			`This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.`
Disable automatic closing of PRs 3 years ago
Update stalebot timings and message 1. Bump up the timings, since the project releases have slowed down a fair bit. 120 days stale with 21 days for a response still gets us the desired effect while loosening the timeline for issue submitters. 2. Revamp the wording to better explain what the author (or others) need to do, and why this bot exists. 5 years ago			`If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or nightlies, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.`

			`This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on [Matrix or Social Media](https://docs.jellyfin.org/general/getting-help.html).`
Add Stale app configuration starting point Link: https://github.com/apps/stale 5 years ago			# Comment to post when closing a stale issue. Set to `false` to disable
			`closeComment: false`
Disable automatic closing of PRs 3 years ago
			`# Disable automatic closing of pull requests`
			`pulls:`
			`daysUntilClose: false`