[ci] add lock workflow to lock issues/PRs with over 150 days of inactivity, to avoid confusion of new version on old issues

Author: TomasVotruba

.github/workflows/lock.yaml

@@ -0,0 +1,29 @@
+name: "Lock closed issues and PRs"
+
+on:
+    schedule:
+        - cron: "0 3 * * *" # every day at 03:00 UTC
+    workflow_dispatch:
+
+jobs:
+    lock:
+        runs-on: ubuntu-latest
+
+        steps:
+            - uses: dessant/lock-threads@v5
+              with:
+                  github-token: ${{ secrets.GITHUB_TOKEN }}
+
+                  issue-inactive-days: 150
+                  pr-inactive-days: 150
+
+                  issue-comment: >
+                      This issue has been automatically locked because it has been closed for 150 days.
+                      Please open a new issue if you have a similar problem.
+
+                  pr-comment: >
+                      This pull request has been automatically locked because it has been closed for 150 days.
+                      Please open a new PR if you want to continue the work.
+
+                  exclude-issue-labels: "keep-open,no-lock"
+                  exclude-pr-labels: "keep-open,no-lock"

.github/workflows/stale.yaml

@@ -14,4 +14,5 @@ jobs:
                   days-before-stale: 60
                   days-before-close: 90
                   stale-issue-message: 'This issue has been automatically marked as stale due to inactivity for past 2 months. It will be closed in next 30 days if no further activity occurs.'
-                  close-issue-message: 'Closing this issue due to prolonged inactivity.'
+                  close-issue-message: 'Closing this issue as inactive for 30 days after marking stale.'
+                  operations-per-run: 10