Add no-response workflow. (#87318)
diff --git a/.github/no-response.yml b/.github/workflows/no-response.yaml
similarity index 62%
rename from .github/no-response.yml
rename to .github/workflows/no-response.yaml
index f7c4233..9970e57 100644
--- a/.github/no-response.yml
+++ b/.github/workflows/no-response.yaml
@@ -1,4 +1,4 @@
-# Configuration for probot-no-response - https://github.com/probot/no-response
+name: No Response
# Number of days of inactivity before an issue is closed for lack of response.
daysUntilClose: 21
@@ -11,10 +11,25 @@
Without additional information, we are unfortunately not sure how to
resolve this issue. We are therefore reluctantly going to close this
bug for now.
-
If you find this problem please file a new issue with the same description,
what happens, logs and the output of 'flutter doctor -v'. All system setups
can be slightly different so it's always better to open new issues and reference
the related ones.
-
Thanks for your contribution.
+
+# Both `issue_comment` and `scheduled` event types are required for this Action
+# to work properly.
+on:
+ issue_comment:
+ types: [created]
+ schedule:
+ # Schedule for five minutes after the hour, every hour
+ - cron: '5 * * * *'
+
+jobs:
+ noResponse:
+ runs-on: ubuntu-latest
+ steps:
+ - uses: lee-dohm/no-response@9bb0a4b5e6a45046f00353d5de7d90fb8bd773bb
+ with:
+ token: ${{ github.token }}
