-
Notifications
You must be signed in to change notification settings - Fork 892
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
chore: update stale.yaml #3674
Conversation
.github/workflows/stale.yaml
Outdated
@@ -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 |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
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
.github/workflows/stale.yaml
Outdated
@@ -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 |
There was a problem hiding this comment.
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
8cab6f3
to
4e5b6d2
Compare
Fixes warning message https://github.com/coder/coder/actions/runs/2915593864