Skip to content

Commit

Permalink
Run stale job hourly
Browse files Browse the repository at this point in the history
The stale job is currently limited to 100 API operations per run to protect against API limits and processing of each stale issue / PR take multiple API calls (commenting, adding or removing tags, closing etc).

It seems like we could bump this up as we have more operations available, but the limit seems to be hourly. Instead, this makes the job run hourly, spreading the work.

After an initial wave of marking and closing stale issues, this should keep the labeling "current" according to the "90 day to stale" configuration.
  • Loading branch information
kassens committed Apr 5, 2024
1 parent 2acfb7b commit 9f3e070
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions .github/workflows/stale.yml
Original file line number Diff line number Diff line change
Expand Up @@ -2,8 +2,8 @@
name: 'Manage stale issues and PRs'
on:
schedule:
# Run daily at 2AM
- cron: '0 2 * * *'
# Run hourly
- cron: '0 * * * *'

jobs:
stale:
Expand All @@ -16,7 +16,7 @@ jobs:
days-before-stale: 90
# Number of days of inactivity before a stale issue or PR is closed
days-before-close: 7
# Number of issues or PRs to process per day
# API calls per run
operations-per-run: 100

# --- Issues ---
Expand All @@ -43,4 +43,4 @@ jobs:
close-pr-message: >
Closing this pull request after a prolonged period of inactivity. If this issue is still present in the latest release, please ask for this pull request to be reopened. Thank you!
# PRs with these labels will never be considered stale
exempt-pr-labels: "Partner,React Core Team,Resolution: Backlog,Type: Bug,Type: Discussion,Type: Needs Investigation,Type: Regression,Type: Feature Request,Type: Enhancement"
exempt-pr-labels: "Partner,React Core Team,Resolution: Backlog,Type: Bug,Type: Discussion,Type: Needs Investigation,Type: Regression,Type: Feature Request,Type: Enhancement"

0 comments on commit 9f3e070

Please sign in to comment.