resource_rules: issues: rules: - name: Mark stale issues with no milestone for closure conditions: date: attribute: updated_at condition: older_than interval_type: months interval: 12 milestone: - No Milestone state: opened actions: labels: - awaiting feedback - auto updated mention: - markglenfletcher comment: | Hi {{author}}, First of all, thank you for raising an issue to help improve the GitLab product. We're sorry about this, but this particular issue has gone unnoticed for quite some time. To establish order in the GitLab-CE Issue Tracker, we must ensure that every issue is correctly labelled and triaged, to get the proper attention. This issue will be closed, as it meets the following criteria: * No activity in the past 12 months * No milestone (unscheduled) We'd like to ask you to help us out and determine whether this issue should be reopened. If this issue is reporting a bug, please can you attempt to reproduce on the latest version of GitLab or GitLab.com, to help us to understand whether the bug still needs our attention. If this issue is proposing a new feature, please can you verify whether the feature proposal is still relevant. Thanks for your help - name: Mark stale issues for closure conditions: date: attribute: updated_at condition: older_than interval_type: months interval: 3 labels: - No Label state: opened actions: labels: - awaiting feedback - auto updated mention: - markglenfletcher comment: | Hi {{author}}, First of all, thank you for raising an issue to help improve the GitLab product. We're sorry about this, but this particular issue has gone unnoticed for quite some time. To establish order in the GitLab-CE Issue Tracker, we must ensure that every issue is correctly labelled and triaged, to get the proper attention. This issue will be closed, as it meets the following criteria: * No activity in the past 3 months * Unlabelled We'd like to ask you to help us out and determine whether this issue should be reopened. If this issue is reporting a bug, please can you attempt to reproduce on the latest version of GitLab or GitLab.com, to help us to understand whether the bug still needs our attention. If this issue is proposing a new feature, please can you verify whether the feature proposal is still relevant. Thanks for your help - name: Close non-updated issues conditions: date: attribute: updated_at condition: older_than interval_type: weeks interval: 2 labels: - awaiting feedback - auto updated state: opened actions: labels: - auto closed mention: - markglenfletcher status: close comment: | {{author}} Closing this issue down in accordance with our [Issue Triage Policies](https://gitlab.com/gitlab-org/triage). Please reopen the issue if you feel that the issue is still relevant. Thanks! - name: Mark potentially interesting feature proposals conditions: labels: - feature proposal state: opened upvotes: attribute: upvotes condition: greater_than threshold: 10 milestone: - No Milestone actions: labels: - auto updated - potential proposal - name: Mark unpopular, old feature proposals for closure conditions: date: attribute: updated_at condition: older_than interval_type: years interval: 1 labels: - feature proposal state: opened upvotes: attribute: upvotes condition: less_than threshold: 10 milestone: - No Milestone actions: labels: - auto updated - awaiting feedback mention: - markglenfletcher comment: | Hi {{author}}, First of all, thank you for raising an issue to help improve the GitLab product. This issue was labelled as a ~"feature proposal" in the past. In order to maintain order in the issue tracker, we are starting to close off old, unpopular feature proposals that have not gained many votes since opening. This issue will be closed, as it meets the following criteria: * No activity in the past 12 months (last update was {{updated_at}}) * Current labels ({{labels}}) include ~"feature proposal" * Unscheduled (not associated with a milestone) * Less than 10 upvotes (currently {{upvotes}} upvotes) Thanks for your help and please raise any new feature proposals as a new issue. - name: Mark very popular, unscheduled feature proposals conditions: labels: - feature proposal state: opened milestone: - No Milestone upvotes: attribute: upvotes condition: greater_than threshold: 50 actions: labels: - auto updated - popular proposal - name: Mark stale bugs for closure conditions: date: attribute: updated_at condition: older_than interval_type: months interval: 6 labels: - bug milestone: - No Milestone state: opened actions: labels: - awaiting feedback - auto updated mention: - markglenfletcher comment: | Hi {{author}}, First of all, thank you for raising an issue to help improve the GitLab product. We're sorry about this, but this particular issue has gone unnoticed for quite some time. To establish order in the GitLab-CE Issue Tracker, we must ensure that every issue is correctly labelled and triaged, to get the proper attention. This issue will be marked for closure, as it meets the following criteria: * Issue is open * No activity in the past 6 months (last update was {{updated_at}}) * Current labels ({{labels}}) include ~bug * Unscheduled (no milestone) We'd like to ask you to help us out and determine whether this issue should be reopened. Because this issue is reporting a bug, please can you attempt to reproduce on the latest version of GitLab or on GitLab.com, to help us to understand whether the bug still needs our attention. Thanks for your help merge_requests: rules: - name: Encourage old Community Merge Requests to completion conditions: date: attribute: updated_at condition: older_than interval_type: months interval: 6 labels: - Community Contribution state: opened actions: labels: - awaiting feedback - auto updated mention: - rymai comment: | Hi {{author}}, First of all, thank you for creating a Merge Request to help improve the GitLab product. We are running through old Merge Requests and asking authors to update their Merge Requests This Merge Request was chosen, as it meets the following criteria: * Open * No activity in the past 6 months (last update was {{updated_at}}) * Current labels ({{labels}}) include ~"Community Contribution" We'd like to ask you to help us out and let us know whether: * You would like to continue the work here * You would like us to take on the Merge Request for you * You would like us to close down the Merge Request Thanks for your help