mirrors/zed
1
0
Fork 0
mirror of https://github.com/zed-industries/zed.git synced 2025-01-12 21:32:40 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 10
zed/.github/workflows/community_close_stale_issues.yml

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

33 lines
1.5 KiB
YAML
Raw Normal View History

Add a rather-conservative stale issue action in dry-run mode (#18233) Zed is becoming more popular and our issue tracker is only growing larger and larger. I realize that a stale issue action can be controversial, but the way we currently manage issues hasn't scaled well and it will only get worse. We need some crowd-sourced system. Let's ask those who have opened issues if their issues are still valid. This is rather conservative and only targets bugs and crashes. I'll run it in debug mode, report the results, and enable it if it feels right. We can always turn this off if users end up really not liking it. My original rules were: ```txt If an issue is old enough (12 months or older) AND if there are no recent comments from the team (last dev comment is older than 6 months) AND it has less than X upvotes (5) AND it does not have an open PR linked to it AND is a "defect" or "panic / crash" AND does not have a "ignore top-ranking issues" label AND was not opened by a org member AND is open AND is issue (not a pull request) THEN close the issue with a kind message. ``` But only some of these were actually supported in the configuration. Release Notes: - N/A
2024-09-23 16:11:26 +00:00
name: "Close Stale Issues"
on:
schedule:
Update close_stale_issues configuration (#18298) @notpeter and I decided on these things: - Give users 10 days to respond - Only run once a week: Tuesday @7AM ET Release Notes: - N/A
2024-09-24 19:42:26 +00:00
- cron: "0 11 * * 2"
Add a rather-conservative stale issue action in dry-run mode (#18233) Zed is becoming more popular and our issue tracker is only growing larger and larger. I realize that a stale issue action can be controversial, but the way we currently manage issues hasn't scaled well and it will only get worse. We need some crowd-sourced system. Let's ask those who have opened issues if their issues are still valid. This is rather conservative and only targets bugs and crashes. I'll run it in debug mode, report the results, and enable it if it feels right. We can always turn this off if users end up really not liking it. My original rules were: ```txt If an issue is old enough (12 months or older) AND if there are no recent comments from the team (last dev comment is older than 6 months) AND it has less than X upvotes (5) AND it does not have an open PR linked to it AND is a "defect" or "panic / crash" AND does not have a "ignore top-ranking issues" label AND was not opened by a org member AND is open AND is issue (not a pull request) THEN close the issue with a kind message. ``` But only some of these were actually supported in the configuration. Release Notes: - N/A
2024-09-23 16:11:26 +00:00
workflow_dispatch:
jobs:
stale:
ci: No GitHub Actions stale check on forks (#20382)
2024-11-07 21:11:18 +00:00
if: github.repository_owner == 'zed-industries'
Add a rather-conservative stale issue action in dry-run mode (#18233) Zed is becoming more popular and our issue tracker is only growing larger and larger. I realize that a stale issue action can be controversial, but the way we currently manage issues hasn't scaled well and it will only get worse. We need some crowd-sourced system. Let's ask those who have opened issues if their issues are still valid. This is rather conservative and only targets bugs and crashes. I'll run it in debug mode, report the results, and enable it if it feels right. We can always turn this off if users end up really not liking it. My original rules were: ```txt If an issue is old enough (12 months or older) AND if there are no recent comments from the team (last dev comment is older than 6 months) AND it has less than X upvotes (5) AND it does not have an open PR linked to it AND is a "defect" or "panic / crash" AND does not have a "ignore top-ranking issues" label AND was not opened by a org member AND is open AND is issue (not a pull request) THEN close the issue with a kind message. ``` But only some of these were actually supported in the configuration. Release Notes: - N/A
2024-09-23 16:11:26 +00:00
runs-on: ubuntu-latest
steps:
Pin actions/stale action to 28ca103 (#18356) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [actions/stale](https://redirect.github.com/actions/stale) | action | pinDigest | -> `28ca103` | --- ### Configuration 📅 **Schedule**: Branch creation - "after 3pm on Wednesday" in timezone America/New_York, Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- Release Notes: - N/A <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOC44MC4wIiwidXBkYXRlZEluVmVyIjoiMzguODAuMCIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOltdfQ==--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2024-09-25 19:25:57 +00:00
- uses: actions/stale@28ca1036281a5e5922ead5184a1bbf96e5fc984e # v9
Add a rather-conservative stale issue action in dry-run mode (#18233) Zed is becoming more popular and our issue tracker is only growing larger and larger. I realize that a stale issue action can be controversial, but the way we currently manage issues hasn't scaled well and it will only get worse. We need some crowd-sourced system. Let's ask those who have opened issues if their issues are still valid. This is rather conservative and only targets bugs and crashes. I'll run it in debug mode, report the results, and enable it if it feels right. We can always turn this off if users end up really not liking it. My original rules were: ```txt If an issue is old enough (12 months or older) AND if there are no recent comments from the team (last dev comment is older than 6 months) AND it has less than X upvotes (5) AND it does not have an open PR linked to it AND is a "defect" or "panic / crash" AND does not have a "ignore top-ranking issues" label AND was not opened by a org member AND is open AND is issue (not a pull request) THEN close the issue with a kind message. ``` But only some of these were actually supported in the configuration. Release Notes: - N/A
2024-09-23 16:11:26 +00:00
with:
repo-token: ${{ secrets.GITHUB_TOKEN }}
stale-issue-message: >
Hi there! 👋
Tell users they can close a stale issue if they can't repro (#19563) A user commented on this issue to let us know they couldn't reproduce, which would keep it open for another 6 months. Best we can do is tell them what to do if they can't repro, which is to close the issue themselves. - https://github.com/zed-industries/zed/issues/10671 Release Notes: - N/A
2024-10-22 17:46:21 +00:00
We're working to clean up our issue tracker by closing older issues that might not be relevant anymore. If you are able to reproduce this issue in the latest version of Zed, please let us know by commenting on this issue, and we will keep it open. If you can't reproduce it, feel free to close the issue yourself. Otherwise, we'll close it in 7 days.
Add a rather-conservative stale issue action in dry-run mode (#18233) Zed is becoming more popular and our issue tracker is only growing larger and larger. I realize that a stale issue action can be controversial, but the way we currently manage issues hasn't scaled well and it will only get worse. We need some crowd-sourced system. Let's ask those who have opened issues if their issues are still valid. This is rather conservative and only targets bugs and crashes. I'll run it in debug mode, report the results, and enable it if it feels right. We can always turn this off if users end up really not liking it. My original rules were: ```txt If an issue is old enough (12 months or older) AND if there are no recent comments from the team (last dev comment is older than 6 months) AND it has less than X upvotes (5) AND it does not have an open PR linked to it AND is a "defect" or "panic / crash" AND does not have a "ignore top-ranking issues" label AND was not opened by a org member AND is open AND is issue (not a pull request) THEN close the issue with a kind message. ``` But only some of these were actually supported in the configuration. Release Notes: - N/A
2024-09-23 16:11:26 +00:00
Thanks for your help!
Fix comment when marking issues as stale (#19561) Oops <img width="928" alt="image" src="https://github.com/user-attachments/assets/a16ea5cd-c02d-4add-9b58-853de9aa5ba7"> Release Notes: - N/A
2024-10-22 17:29:48 +00:00
close-issue-message: "This issue was closed due to inactivity. If you're still experiencing this problem, please open a new issue with a link to this issue."
Tweak close stale issues configuration (#18275) Release Notes: - N/A
2024-09-24 13:15:25 +00:00
# We will increase `days-before-stale` to 365 on or after Jan 24th,
# 2024. This date marks one year since migrating issues from
# 'community' to 'zed' repository. The migration added activity to all
# issues, preventing 365 days from working until then.
Update stale issues configuration to use 180 days (#18238) Release Notes: - N/A
2024-09-23 16:32:31 +00:00
days-before-stale: 180
Close stale issues out after 7 days (#18707) Closes #ISSUE Release Notes: - N/A
2024-10-03 18:38:49 +00:00
days-before-close: 7
ci: Update issue templates. Rename defect to bug and improve log formatting (#20246)
2024-11-05 17:07:17 +00:00
any-of-issue-labels: "bug,panic / crash"
Bump operations-per-run parameter in stale issues action (#18276) Release Notes: - N/A
2024-09-24 13:44:27 +00:00
operations-per-run: 1000
Add a rather-conservative stale issue action in dry-run mode (#18233) Zed is becoming more popular and our issue tracker is only growing larger and larger. I realize that a stale issue action can be controversial, but the way we currently manage issues hasn't scaled well and it will only get worse. We need some crowd-sourced system. Let's ask those who have opened issues if their issues are still valid. This is rather conservative and only targets bugs and crashes. I'll run it in debug mode, report the results, and enable it if it feels right. We can always turn this off if users end up really not liking it. My original rules were: ```txt If an issue is old enough (12 months or older) AND if there are no recent comments from the team (last dev comment is older than 6 months) AND it has less than X upvotes (5) AND it does not have an open PR linked to it AND is a "defect" or "panic / crash" AND does not have a "ignore top-ranking issues" label AND was not opened by a org member AND is open AND is issue (not a pull request) THEN close the issue with a kind message. ``` But only some of these were actually supported in the configuration. Release Notes: - N/A
2024-09-23 16:11:26 +00:00
ascending: true
enable-statistics: true
stale-issue-label: "stale"
Reference in a new issue Copy permalink