diff --git a/.github/issue-close-app.yml b/.github/issue-close-app.yml
deleted file mode 100644
index 7149031..0000000
--- a/.github/issue-close-app.yml
+++ /dev/null
@@ -1,16 +0,0 @@
-# Comment that will be sent if an issue is judged to be closed.
-comment: "This issue has been closed because it does not meet our Issue template. Please read our [guidelines for contributing](https://github.com/next-theme/hexo-theme-next/blob/master/.github/CONTRIBUTING.md#how-can-i-contribute)."
-issueConfigs:
-# There can be several configs for different kind of issues.
-- content:
-  - "Issue Checklist"
-# Optional configuration:
-#
-# whether the keywords are case-insensitive
-# default value is false, which means keywords are case-sensitive
-caseInsensitive: true
-# the label that will be added when the bot close an issue
-# The bot will only add a label if this property is set.
-label: "Invalid"
-# The issue is judged to be legal if it includes all keywords from any of these two configs.
-# Or it will be closed by the app.
diff --git a/.github/lock.yml b/.github/lock.yml
deleted file mode 100644
index b2564db..0000000
--- a/.github/lock.yml
+++ /dev/null
@@ -1,38 +0,0 @@
-# Configuration for Lock Threads - https://github.com/dessant/lock-threads
-
-# Number of days of inactivity before a closed issue or pull request is locked
-daysUntilLock: 365
-
-# Skip issues and pull requests created before a given timestamp. Timestamp must
-# follow ISO 8601 (`YYYY-MM-DD`). Set to `false` to disable
-skipCreatedBefore: false
-
-# Issues and pull requests with these labels will be ignored. Set to `[]` to disable
-exemptLabels: []
-
-# Label to add before locking, such as `outdated`. Set to `false` to disable
-lockLabel: false
-
-# Comment to post before locking. Set to `false` to disable
-lockComment: >
-  This thread has been automatically locked since there has not been
-  any recent activity after it was closed. It is possible issue was
-  solved or at least outdated. Feel free to open new for related bugs.
-
-# Assign `resolved` as the reason for locking. Set to `false` to disable
-setLockReason: true
-
-# Limit to only `issues` or `pulls`
-only: issues
-
-# Optionally, specify configuration settings just for `issues` or `pulls`
-# issues:
-#   exemptLabels:
-#     - help-wanted
-#   lockLabel: outdated
-
-# pulls:
-#   daysUntilLock: 30
-
-# Repository to extend settings from
-# _extends: repo
diff --git a/.github/workflows/lock.yml b/.github/workflows/lock.yml
new file mode 100644
index 0000000..8d8b463
--- /dev/null
+++ b/.github/workflows/lock.yml
@@ -0,0 +1,19 @@
+# Configuration for Lock Threads - https://github.com/dessant/lock-threads
+name: 'Lock threads'
+
+on:
+  schedule:
+    - cron: '0 0 * * *'
+
+jobs:
+  lock:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: dessant/lock-threads@v2
+        with:
+          github-token: ${{ github.token }}
+          issue-lock-comment: >
+            This thread has been automatically locked since there has not been
+            any recent activity after it was closed. It is possible issue was
+            solved or at least outdated. Feel free to open new for related bugs.
+          process-only: 'issues'