Skip to content

chore: add new label for stale automation #1390

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.

Sign up for GitHub

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
Mar 31, 2023
Merged

chore: add new label for stale automation #1390

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .github/workflows/stale-issues.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,8 +23,8 @@ jobs:
close-issue-reason: not_planned
# Exempt any issue that hasn't been triaged yet, or that is clearly labeled
exempt-issue-labels: triage,status/confirmed,status/blocked,status/on-hold,status/completed
# Include only issues that were labeled as `need-customer-feedback` (aka only issues that need more info from the customer)
only-issue-labels: need-customer-feedback
# Include only issues that were labeled as `need-response` (aka only issues that need a response from the customer)
only-issue-labels: need-response
# Settings specific to issues
days-before-issue-stale: 14
days-before-issue-close: 7
Expand Down
6 changes: 3 additions & 3 deletions MAINTAINERS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -103,7 +103,8 @@ These are the most common labels used by maintainers to triage issues, pull requ
| good-first-issue | Something that is suitable for those who want to start contributing | |
| help-wanted | Tasks you want help from anyone to move forward | Bandwidth, complex topics, etc. |
| need-customer-feedback | Tasks that need more feedback before proceeding | 80/20% rule, uncertain, etc. |
| need-more-information | Missing information before making any calls | Triggers stale automation after 2 weeks |
| need-more-information | Missing information before making any calls | Signal that investigation or answers are needed |
| need-response | Requires a response from a customer and might be automatically closed if none is received | Marked as stale after 2 weeks, and closed after 3 |
| need-issue | PR is missing a related issue for tracking change | |

## Maintainer Responsibilities
Expand Down Expand Up @@ -269,8 +270,7 @@ In other cases, you may have constrained capacity. Use `help-wanted` label when

When in doubt, use `need-more-information` or `need-customer-feedback` labels to signal more context and feedback are necessary before proceeding. You can also use `status/on-hold` label when you expect it might take a while to gather enough information before you can decide.

Note that issues marked as `need-customer-feedback` will be
automatically closed after 3 weeks of inactivity.
Note that issues marked as `need-response` will be automatically closed after 3 weeks of inactivity.

### Crediting contributions

Expand Down