qBittorrent/.github/workflows/stale_bot.yaml

name: Stale bot

on:
  schedule:
    - cron: '0 0 * * *'

permissions:
  pull-requests: write

jobs:
  stale:
    runs-on: ubuntu-latest
    steps:
      - name: Mark and close stale PRs
        uses: actions/stale@v5
        with:
          stale-pr-message: "This PR is stale because it has been 60 days with no activity. This PR will be automatically closed within 7 days if there is no further activity."
          close-pr-message: "This PR was closed because it has been stalled for some time with no activity."
          days-before-stale: -1 # avoid marking issues
          days-before-pr-stale: 60
          days-before-close: -1 # avoid closing issues
          days-before-pr-close: 7
          exempt-all-pr-assignees: true  # avoid stale for all PR with assignees
          exempt-all-pr-milestones: true # avoid stale for all PR with milestones
          operations-per-run: 200
Introduce stale bot for PR (#15211) Stale bot will mark stale PR with a tag and close them after a specified interval of time. * Draft PRs are not subject to this marking. * PR with an assignee or milestone is not subject to this marking. 3 years ago			`name: Stale bot`

			`on:`
			`schedule:`
			`- cron: '0 0 * * *'`

GHA CI: use least permission level `actions: write` is required by Chocobo1/setup-ccache-action. `pull-requests: write` is required by actions/stale. https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#permissions 2 years ago			`permissions:`
			`pull-requests: write`

Introduce stale bot for PR (#15211) Stale bot will mark stale PR with a tag and close them after a specified interval of time. * Draft PRs are not subject to this marking. * PR with an assignee or milestone is not subject to this marking. 3 years ago			`jobs:`
			`stale:`
			`runs-on: ubuntu-latest`
			`steps:`
			`- name: Mark and close stale PRs`
GHA CI: Update `stale` action to `v5` 3 years ago			`uses: actions/stale@v5`
Introduce stale bot for PR (#15211) Stale bot will mark stale PR with a tag and close them after a specified interval of time. * Draft PRs are not subject to this marking. * PR with an assignee or milestone is not subject to this marking. 3 years ago			`with:`
			`stale-pr-message: "This PR is stale because it has been 60 days with no activity. This PR will be automatically closed within 7 days if there is no further activity."`
			`close-pr-message: "This PR was closed because it has been stalled for some time with no activity."`
			`days-before-stale: -1 # avoid marking issues`
			`days-before-pr-stale: 60`
			`days-before-close: -1 # avoid closing issues`
			`days-before-pr-close: 7`
			`exempt-all-pr-assignees: true # avoid stale for all PR with assignees`
			`exempt-all-pr-milestones: true # avoid stale for all PR with milestones`
Handle more PR per run Previously only about ~27 PR are scanned per run, this commit attempt to handle all open PR at once. 3 years ago			`operations-per-run: 200`