chore: add workflow to close stale issues needing more info#882
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
There was a problem hiding this comment.
Pull request overview
Adds an automated GitHub Issues follow-up process for issues labeled needs-more-info, including documentation and issue templates to set expectations for reporters.
Changes:
- Introduces a scheduled
actions/staleworkflow to warn (after 10 days) and close (after 14 days total) issues needing more info. - Adds an
issue_commentworkflow to removeneeds-more-info/stale-warnedwhen the original author responds and post an acknowledgement. - Updates contributor docs and adds bug/feature issue templates to describe the follow-up process.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
| CONTRIBUTING.md | Documents the “needs more info” follow-up and closure timeline. |
| .github/workflows/stale-issues.yml | Scheduled workflow to label/close stale needs-more-info issues and emit a step summary. |
| .github/workflows/remove-needs-info-on-response.yml | Automation to remove labels on author response and post a thank-you comment. |
| .github/ISSUE_TEMPLATE/feature_request.md | Feature request template including follow-up expectations. |
| .github/ISSUE_TEMPLATE/bug_report.md | Bug report template including follow-up expectations and security guidance. |
Comments suppressed due to low confidence (1)
.github/workflows/remove-needs-info-on-response.yml:40
- This removes the
needs-more-infolabel and posts a message implying the requested details were provided on any comment by the issue author. That conflicts with the documented “Need more time?” flow (where the author may be acknowledging they need time but hasn't provided details yet) and may prematurely take the issue out of theneeds-more-infoqueue. Consider either (a) only removingstale-warnedon any author response and keepingneeds-more-infountil a maintainer removes it, or (b) requiring an explicit command/keyword to removeneeds-more-info, and tailoring the auto-reply text accordingly.
run: |
gh issue edit "$ISSUE_NUMBER" --remove-label "needs-more-info" --repo "$REPO"
# Remove stale-warned if present (user may have responded after receiving the warning)
gh issue edit "$ISSUE_NUMBER" --remove-label "stale-warned" --repo "$REPO" 2>/dev/null || true
- name: Post thank you comment
run: |
gh issue comment "$ISSUE_NUMBER" --repo "$REPO" --body \
"Hi there, thanks for providing the additional information! We've received your update and will review it shortly. We appreciate your help in making Sanity plugins better!"
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Description
Duplicates the needs more info workflows from sanity monorepo sanity-io/sanity#12015
What to review
Testing