blockworks-foundation
/
solana
mirror of https://github.com/blockworks-foundation/solana.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Remove `start-date` config from Stalebot 

This doesn't actually do what I thought it did. The `start-date` config doesn't make stalebot start from a certain date forward, it makes tasks older than that date immune to being closed.

This means I'm going to just have to find a way to raise the GitHub API operations limit to be able to handle more tasks, or wait until enough have been closed that it fits within our current limit.
This commit is contained in:
Steven Luscher 2022-12-19 23:02:32 -08:00 committed by GitHub
parent 0b479066b3
commit 92c90271ab
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 0 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.github/workflows/manage-stale-issues-and-prs.yml vendored
View File

@ -37,7 +37,3 @@ jobs:
stale-issue-message: "" # Leave no comment when marking as stale
stale-pr-label: stale
stale-pr-message: "" # Leave no comment when marking as stale
# Time immemorial when in debug-only mode (ie. on pull requests).
# `STALEBOT_START_DATE` otherwise.
# You can use this as a killswitch by setting `STALEBOT_START_DATE` in the far future.
start-date: ${{ github.event_name == 'pull_request' && '1970-01-01T00:00:00Z' || secrets.STALEBOT_START_DATE_RFC_2822 }} # ISO 8601 or RFC 2822