- Notifications
You must be signed in to change notification settings - Fork673
docs: update CONTRIBUTING.rst with policy on issue management#3219
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Also update the `stale` job to close issues with no activity, unlessthey are assigned to someone.
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.
Pull Request Overview
This PR clarifies issue management policy in the contributing guide and updates the stale workflow to exempt assigned issues and augment stale/close messages with community contribution guidance.
- Add a new “Issue Management and Our Approach to Contributions” section in CONTRIBUTING.rst
- Exempt assigned issues from the stale bot and expand stale/closure messages in .github/workflows/stale.yml
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| CONTRIBUTING.rst | New policy section on inactive issues, reopening, and community ownership |
| .github/workflows/stale.yml | Addedexempt-all-assignees, expanded stale and close messages |
Comments suppressed due to low confidence (1)
.github/workflows/stale.yml:24
- It appears the original any-of-labels setting was removed when introducing exempt-all-assignees. Without re-adding any-of-labels, the bot may no longer filter by 'need info', 'Waiting for response', or 'stale' before marking issues. Consider restoring the any-of-labels configuration if that filtering is still required.
exempt-all-assignees: trueThere 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.
Thanks@JohnVillalovos, let's see how the first run goes!
45dda50 intomainUh oh!
There was an error while loading.Please reload this page.
@nejch It wasn't too bad. Marked around 7 or so issues as stale. And one got a comment, so it should get unmarked as stale on the next run. |
Also update the
stalejob to close issues with no activity, unless they are assigned to someone.