Skip to content

Commit

Permalink
Migrate from probot/no-response to lee-dohm/no-response (#13891)
Browse files Browse the repository at this point in the history
Close #13472
  • Loading branch information
fisker committed Nov 24, 2022
1 parent a60bee2 commit 38806fe
Show file tree
Hide file tree
Showing 5 changed files with 35 additions and 14 deletions.
10 changes: 0 additions & 10 deletions .github/no-response.yml

This file was deleted.

4 changes: 2 additions & 2 deletions .github/workflows/bundler-friendly.yml
Expand Up @@ -2,8 +2,8 @@ name: Bundler_Friendly

on:
schedule:
# “At 00:00 on Sunday.” https://crontab.guru/#0%C2%A00%C2%A0*%C2%A0*%C2%A00
- cron: "0 0 * * 0"
# “At 00:00 on Sunday.” https://crontab.guru/#0_0_*_*_SUN
- cron: "0 0 * * SUN"
pull_request:
paths:
- "scripts/tools/bundle-test/**"
Expand Down
4 changes: 2 additions & 2 deletions .github/workflows/dev-package-test.yml
Expand Up @@ -2,8 +2,8 @@ name: Dev_Package_Test

on:
schedule:
# “At 00:00 on Sunday.” https://crontab.guru/#0%C2%A00%C2%A0*%C2%A0*%C2%A00
- cron: "0 0 * * 0"
# “At 00:00 on Sunday.” https://crontab.guru/#0_0_*_*_SUN
- cron: "0 0 * * SUN"
pull_request:
paths:
- "package.json"
Expand Down
1 change: 1 addition & 0 deletions .github/workflows/lock.yml
Expand Up @@ -2,6 +2,7 @@ name: "Lock"

on:
schedule:
# “At 00:00.” https://crontab.guru/#0_0_*_*_*
- cron: "0 0 * * *"

jobs:
Expand Down
30 changes: 30 additions & 0 deletions .github/workflows/no-response.yml
@@ -0,0 +1,30 @@
name: No Response

# Both `issue_comment` and `scheduled` event types are required for this Action
# to work properly.
on:
issue_comment:
types:
- created
schedule:
# “At minute 0.” https://crontab.guru/#0_*_*_*_*
- cron: "0 * * * *"

permissions:
issues: write

jobs:
no-response:
runs-on: ubuntu-latest
steps:
- uses: lee-dohm/no-response@v0.5.0
with:
token: ${{ github.token }}
daysUntilClose: 14
responseRequiredLabel: "status:awaiting response"
closeComment: >
This issue has been automatically closed because there has been no response
to our request for more information from the original author. With only the
information that is currently in the issue, we don't have enough information
to take action. Please reach out if you have or find the answers we need so
that we can investigate further.

0 comments on commit 38806fe

Please sign in to comment.