fish-shell/.github/workflows/lockthreads.yml

name: 'Lock threads'

on:
  schedule:
    - cron: '0 18 * * 1'
#            │ │  │ │ │
#   min 0-59 ┘ │  │ │ └ weekday 0-6
#    hour 0-23 ┘  │ └ month 1-12
#                 └ day 1-31
jobs:
  lock:
    runs-on: ubuntu-latest
    steps:
      - uses: dessant/lock-threads@v2
        with:
          github-token: ${{ github.token }}
          issue-lock-inactive-days: '365'
          pr-lock-inactive-days: '365'
          issue-exclude-labels: 'question, needs more info'
Automatically lock closed issues/prs after 90 days We've been getting a bunch of comments on old closed issues. Instead people should create new ones. This adds a github "workflow" that should lock closed issues/prs after 90 days, except those labelled "question". Let's see how it works out. 2020-04-16 18:53:21 +02:00			`name: 'Lock threads'`

			`on:`
			`schedule:`
Update lockthreads.yml exclude RFCs, enhancement requests, have it run weekly. 2021-11-02 09:43:47 -07:00			`- cron: '0 18 * * 1'`
			`# │ │ │ │ │`
			`# min 0-59 ┘ │ │ │ └ weekday 0-6`
			`# hour 0-23 ┘ │ └ month 1-12`
			`# └ day 1-31`
Automatically lock closed issues/prs after 90 days We've been getting a bunch of comments on old closed issues. Instead people should create new ones. This adds a github "workflow" that should lock closed issues/prs after 90 days, except those labelled "question". Let's see how it works out. 2020-04-16 18:53:21 +02:00			`jobs:`
			`lock:`
			`runs-on: ubuntu-latest`
			`steps:`
			`- uses: dessant/lock-threads@v2`
			`with:`
			`github-token: ${{ github.token }}`
Adjust the GitHub thread locker script. Set locked thread inactivity count to default 365. Add 'needs more info' as an obvious on its face exception. The default seems quite an inconventient, very strict thing t do: it will lock threads that are closed and quiet because they have been quiet and closed. This seems to make it hard to talk about issues after they are closed or contribute. I can as a fish-shell contributor, but that's not really the point. Practically, right now to reply to any PR or any issue fixed in July, well you can't. 2021-10-24 04:38:06 -07:00			`issue-lock-inactive-days: '365'`
			`pr-lock-inactive-days: '365'`
Lock enhancements and RFCs again The point here is to let issues be done, and have any new discussions happen in new issues so you can decouple the context. This revert pending further discussion. 2021-11-02 18:15:30 +01:00			`issue-exclude-labels: 'question, needs more info'`