system/NetworkManager
system/NetworkManager
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/NetworkManager/NetworkManager synced 2024-07-08 19:55:47 +00:00
Code Issues Packages Projects Releases Wiki Activity
f58b281ef4
NetworkManager/.triage-policies.yml

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

38 lines
1.1 KiB
YAML
Raw Normal View History

gitlab-ci: add scheduled pipeline to triage inactive issues and MRs
2020-03-18 15:01:30 +00:00
host_url: https://gitlab.freedesktop.org
resource_rules:
issues:
rules:
triage: only make stale issues/merge-requests with a label instead of autoclosing them An issue/merge-requests only moves forward by a human putting effort in. Wether the issue is open, closed, autoclosed or flagged with a "stale" label doesn't matter in theory. In practice, humans don't like getting their issues/merge-requests autoclosed. Instead, add a "stale" label. There was always a benefit of this automatic action. It tended to generate some feedback and new action. Sometimes it even brought new attention to the issue/merge-request to get it fixed. That is hopefully also the case with the stale label.
2023-05-05 14:04:55 +00:00
- name: Mark issue as stale with no activity for 4 months
gitlab-ci: add scheduled pipeline to triage inactive issues and MRs
2020-03-18 15:01:30 +00:00
conditions:
date:
attribute: updated_at
condition: older_than
interval_type: months
triage: only make stale issues/merge-requests with a label instead of autoclosing them An issue/merge-requests only moves forward by a human putting effort in. Wether the issue is open, closed, autoclosed or flagged with a "stale" label doesn't matter in theory. In practice, humans don't like getting their issues/merge-requests autoclosed. Instead, add a "stale" label. There was always a benefit of this automatic action. It tended to generate some feedback and new action. Sometimes it even brought new attention to the issue/merge-request to get it fixed. That is hopefully also the case with the stale label.
2023-05-05 14:04:55 +00:00
interval: 4
gitlab-ci: add scheduled pipeline to triage inactive issues and MRs
2020-03-18 15:01:30 +00:00
state: opened
triage: only make stale issues/merge-requests with a label instead of autoclosing them An issue/merge-requests only moves forward by a human putting effort in. Wether the issue is open, closed, autoclosed or flagged with a "stale" label doesn't matter in theory. In practice, humans don't like getting their issues/merge-requests autoclosed. Instead, add a "stale" label. There was always a benefit of this automatic action. It tended to generate some feedback and new action. Sometimes it even brought new attention to the issue/merge-request to get it fixed. That is hopefully also the case with the stale label.
2023-05-05 14:04:55 +00:00
forbidden_labels:
- stale
gitlab-ci: add scheduled pipeline to triage inactive issues and MRs
2020-03-18 15:01:30 +00:00
actions:
comment: |
triage: only make stale issues/merge-requests with a label instead of autoclosing them An issue/merge-requests only moves forward by a human putting effort in. Wether the issue is open, closed, autoclosed or flagged with a "stale" label doesn't matter in theory. In practice, humans don't like getting their issues/merge-requests autoclosed. Instead, add a "stale" label. There was always a benefit of this automatic action. It tended to generate some feedback and new action. Sometimes it even brought new attention to the issue/merge-request to get it fixed. That is hopefully also the case with the stale label.
2023-05-05 14:04:55 +00:00
This issue has been inactive for 4 months and got stale. Contributions welcome to move it forward.
gitlab-ci: add scheduled pipeline to triage inactive issues and MRs
2020-03-18 15:01:30 +00:00
labels:
triage: only make stale issues/merge-requests with a label instead of autoclosing them An issue/merge-requests only moves forward by a human putting effort in. Wether the issue is open, closed, autoclosed or flagged with a "stale" label doesn't matter in theory. In practice, humans don't like getting their issues/merge-requests autoclosed. Instead, add a "stale" label. There was always a benefit of this automatic action. It tended to generate some feedback and new action. Sometimes it even brought new attention to the issue/merge-request to get it fixed. That is hopefully also the case with the stale label.
2023-05-05 14:04:55 +00:00
- stale
gitlab-ci: add scheduled pipeline to triage inactive issues and MRs
2020-03-18 15:01:30 +00:00
merge_requests:
rules:
triage: only make stale issues/merge-requests with a label instead of autoclosing them An issue/merge-requests only moves forward by a human putting effort in. Wether the issue is open, closed, autoclosed or flagged with a "stale" label doesn't matter in theory. In practice, humans don't like getting their issues/merge-requests autoclosed. Instead, add a "stale" label. There was always a benefit of this automatic action. It tended to generate some feedback and new action. Sometimes it even brought new attention to the issue/merge-request to get it fixed. That is hopefully also the case with the stale label.
2023-05-05 14:04:55 +00:00
- name: Mark merge-request as stale after no activity for 2 months
gitlab-ci: add scheduled pipeline to triage inactive issues and MRs
2020-03-18 15:01:30 +00:00
conditions:
date:
attribute: updated_at
condition: older_than
interval_type: months
interval: 2
state: opened
triage: only make stale issues/merge-requests with a label instead of autoclosing them An issue/merge-requests only moves forward by a human putting effort in. Wether the issue is open, closed, autoclosed or flagged with a "stale" label doesn't matter in theory. In practice, humans don't like getting their issues/merge-requests autoclosed. Instead, add a "stale" label. There was always a benefit of this automatic action. It tended to generate some feedback and new action. Sometimes it even brought new attention to the issue/merge-request to get it fixed. That is hopefully also the case with the stale label.
2023-05-05 14:04:55 +00:00
forbidden_labels:
- stale
gitlab-ci: add scheduled pipeline to triage inactive issues and MRs
2020-03-18 15:01:30 +00:00
actions:
comment: |
triage: only make stale issues/merge-requests with a label instead of autoclosing them An issue/merge-requests only moves forward by a human putting effort in. Wether the issue is open, closed, autoclosed or flagged with a "stale" label doesn't matter in theory. In practice, humans don't like getting their issues/merge-requests autoclosed. Instead, add a "stale" label. There was always a benefit of this automatic action. It tended to generate some feedback and new action. Sometimes it even brought new attention to the issue/merge-request to get it fixed. That is hopefully also the case with the stale label.
2023-05-05 14:04:55 +00:00
This merge-request has been inactive for 2 months and got stale. Work is necessary to move it forward.
gitlab-ci: add scheduled pipeline to triage inactive issues and MRs
2020-03-18 15:01:30 +00:00
labels:
triage: only make stale issues/merge-requests with a label instead of autoclosing them An issue/merge-requests only moves forward by a human putting effort in. Wether the issue is open, closed, autoclosed or flagged with a "stale" label doesn't matter in theory. In practice, humans don't like getting their issues/merge-requests autoclosed. Instead, add a "stale" label. There was always a benefit of this automatic action. It tended to generate some feedback and new action. Sometimes it even brought new attention to the issue/merge-request to get it fixed. That is hopefully also the case with the stale label.
2023-05-05 14:04:55 +00:00
- stale
Reference in New Issue Copy Permalink