-
Notifications
You must be signed in to change notification settings - Fork 369
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support different number of days for PRs and issues #214
Comments
The bot does not seem to run reliably, so try the action instead. There is downside that the action does not support different limits for issues and PRs. See probot/stale#308 See actions/stale#214
@nijel I like the idea but IMO the first one is more simple to understand. |
I will provide a PR. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days |
Up |
Now that actions/stale#214 is implemented we can set desired limits.
@hross any chance you folks could tag a stale release for this, or should we just pin to specific hashes? |
@alyssawilk yup, I am letting it run internally to make sure we don't run into anything before I up the hash. |
Awesome, thanks for the update! |
I'm currently using Probot Stale and would like to migrate to this action. One thing which doesn't seem to be possible to configure here is different number of days for PRs and issues.
I can see two approaches that would work for me:
issue-days-before-stale
/pr-days-before-stale
andissue-days-before-close
/pr-days-before-close
settings to overridedays-before-stale
anddays-before-close
process-issue
/process-pr
boolean flags to disable processing of given types and I'd configure two action runsI think second approach is better as that makes it easy to diverge any setting for PR and issues while not making the action more complex with every single such diversion.
The text was updated successfully, but these errors were encountered: