Skip to content

Commit

Permalink
Stop No Response action running when unneeded.
Browse files Browse the repository at this point in the history
1) The No Response action is running every 5 minutes, wasting CPU. Once a day is plenty.

2) If you fork the repository in order to contribute, and you want the CI test actions to run on each commit, you can inherit the original actions from the main repo. However, that also inherits No Response action, which can't run without an issue tracker. As a result, you receive a spurious error email every time No Response runs. While it is possible to individually exclude actions with some sort of regular expression parameter in the GitHub web-site, it is neater to have the action automatically skip if it isn't in the Kivy/* domain.
  • Loading branch information
Julian-O committed Dec 10, 2023
1 parent 6fcea49 commit e317376
Showing 1 changed file with 4 additions and 2 deletions.
6 changes: 4 additions & 2 deletions .github/workflows/no-response.yml
Original file line number Diff line number Diff line change
Expand Up @@ -6,11 +6,13 @@ on:
issue_comment:
types: [created]
schedule:
# Schedule for five minutes after the hour, every hour
- cron: '5 * * * *'
# Schedule for an arbitrary time (5am) once every day
- cron: '* 5 * * *'

jobs:
noResponse:
# Don't run if in a fork
if: github.repository_owner == 'kivy'
runs-on: ubuntu-latest
steps:
- uses: lee-dohm/no-response@9bb0a4b5e6a45046f00353d5de7d90fb8bd773bb
Expand Down

0 comments on commit e317376

Please sign in to comment.