Skip to content

chore: update stale.yaml #3674

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

Merged
merged 1 commit into from
Aug 24, 2022
Merged

chore: update stale.yaml #3674

merged 1 commit into from
Aug 24, 2022

Conversation

jsjoeio
Copy link
Contributor

@jsjoeio jsjoeio commented Aug 24, 2022

@jsjoeio jsjoeio added the chore label Aug 24, 2022
@jsjoeio jsjoeio self-assigned this Aug 24, 2022
@jsjoeio jsjoeio requested review from ammario and kylecarbs August 24, 2022 17:35
@@ -20,7 +20,8 @@ jobs:
# Pull Requests become stale more quickly due to merge conflicts.
# Also, we promote minimizing WIP.
days-before-pr-stale: 7
days-before-pr-close: 3
days-before-issue-stale: 30
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Default value is 60 which feels too long if we want to keep issue count small. Is 30 too aggressive?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think 60 (or even 90) are better knobs based on my past experiences with stale bots. I worry that at 30 the stale bot spam will be more annoying than the issue count.

Based on pulse, the issue count has been shrinking naturally, so I don't think we should make this change.
Screen Shot 2022-08-24 at 12 49 31 PM

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good data to back that up. I will remove

@@ -20,7 +20,6 @@ jobs:
# Pull Requests become stale more quickly due to merge conflicts.
# Also, we promote minimizing WIP.
days-before-pr-stale: 7
days-before-pr-close: 3
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That shouldn't have been deleted, one second

- remove close-issue-reason (only valid in 5.1.0)
- add days-before-issue-stale 30
@jsjoeio jsjoeio merged commit 254e91a into main Aug 24, 2022
@jsjoeio jsjoeio deleted the jsjoeio-patch-1 branch August 24, 2022 19:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants