system/NetworkManager
system/NetworkManager
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/NetworkManager/NetworkManager synced 2024-07-01 07:04:56 +00:00
Code Issues Packages Projects Releases Wiki Activity
73602b9d98
NetworkManager/.triage-policies.yml

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

185 lines
5.2 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:
Explain new issues workflow and add triage automation Add explanation of how to indicate the new issues workflow to MAINTAINERS.md: triage -> investigation -> devel. The different stages are indicated using Gitlab's scoped labels (mutually exclusive). These stages try to hightlight that the issue cannot be fixed and it's not moving forward because more info is needed, already. Also, add a section to CONTRIBUTING.md highlighting the importance of helping in the triage and investigation stages: developers often cannot fix bugs because lack of time to investigate, but even users that doesn't know how to fix it due to lack of knowledge of the code base can help thanks to their knowledge on networking. Finally, make the 'triage:issues' CI job to work again, adding some new policies with new automations. The automation will add or remove the labels: stale, help-needed::{triage, investigation, devel} and unassigned. The labels help-needed::* and unassigned will be automatically added to all issues without an assignee. This reflects better the reality of not having enough time to work on most of the issues unless there is some external help.
2024-05-23 09:55:52 +00:00
- name: Set initial workflow stage
conditions:
state: opened
forbidden_labels:
- workflow::triage
- workflow::investigation
- workflow::devel
actions:
labels:
- workflow::triage
- name: Ensure that only one workflow label is used (1/2)
conditions:
state: opened
labels:
- workflow::triage
- workflow::investigation
forbidden_labels:
- workflow::devel
actions:
remove_labels:
- workflow::triage
- name: Ensure that only one workflow label is used (1/2)
conditions:
state: opened
labels:
- workflow::{triage, investigation}
- workflow::devel
actions:
remove_labels:
- workflow::triage
- workflow::investigation
- name: Remove help-needed::* and unassigned labels on assigned issue
conditions:
state: opened
ruby: resource["assignees"].length > 0
labels:
- help-needed::{triage, investigation, devel}
- unassigned
actions:
remove_labels:
- help-needed::triage
- help-needed::investigation
- help-needed::devel
- unassigned
- name: Add help-needed::triage and unassigned labels on unassigned issues
conditions:
state: opened
ruby: resource["assignees"].length == 0
labels:
- workflow::triage
forbidden_labels:
- help-needed::triage
- unassigned
actions:
labels:
- help-needed::triage
- unassigned
- name: Remove wrong help-needed::* labels for issues on triage stage
conditions:
state: opened
labels:
- workflow::triage
- help-needed::{investigation, devel}
actions:
remove_labels:
- help-needed::investigation
- help-needed::devel
- name: Add help-needed::investigation and unassigned labels on unassigned issues
conditions:
state: opened
ruby: resource["assignees"].length == 0
labels:
- workflow::investigation
forbidden_labels:
- help-needed::investigation
- unassigned
actions:
labels:
- help-needed::investigation
- unassigned
- name: Remove wrong help-needed::* labels for issues on investigation stage
conditions:
state: opened
labels:
- workflow::investigation
- help-needed::{triage, devel}
actions:
remove_labels:
- help-needed::triage
- help-needed::devel
- name: Add help-needed::devel and unassigned labels on unassigned issues
conditions:
state: opened
ruby: resource["assignees"].length == 0
labels:
- workflow::devel
forbidden_labels:
- help-needed::devel
- unassigned
actions:
labels:
- help-needed::devel
- unassigned
- name: Remove wrong help-needed::* labels for issues on devel stage
conditions:
state: opened
labels:
- workflow::devel
- help-needed::{triage, investigation}
actions:
remove_labels:
- help-needed::triage
- help-needed::investigation
- name: Remove triage::* labels if the issue is not triaged
conditions:
state: opened
labels:
- workflow::triage
- triaged::{bug, RFE}
actions:
remove_labels:
- triaged::bug
- triaged::RFE
- name: Ensure that only one triaged::* label is used
conditions:
state: opened
labels:
- triaged::bug
- triaged::RFE
actions:
remove_labels:
- triaged::RFE
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:
Explain new issues workflow and add triage automation Add explanation of how to indicate the new issues workflow to MAINTAINERS.md: triage -> investigation -> devel. The different stages are indicated using Gitlab's scoped labels (mutually exclusive). These stages try to hightlight that the issue cannot be fixed and it's not moving forward because more info is needed, already. Also, add a section to CONTRIBUTING.md highlighting the importance of helping in the triage and investigation stages: developers often cannot fix bugs because lack of time to investigate, but even users that doesn't know how to fix it due to lack of knowledge of the code base can help thanks to their knowledge on networking. Finally, make the 'triage:issues' CI job to work again, adding some new policies with new automations. The automation will add or remove the labels: stale, help-needed::{triage, investigation, devel} and unassigned. The labels help-needed::* and unassigned will be automatically added to all issues without an assignee. This reflects better the reality of not having enough time to work on most of the issues unless there is some external help.
2024-05-23 09:55:52 +00:00
state: opened
gitlab-ci: add scheduled pipeline to triage inactive issues and MRs
2020-03-18 15:01:30 +00:00
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
forbidden_labels:
- stale
gitlab-ci: add scheduled pipeline to triage inactive issues and MRs
2020-03-18 15:01:30 +00:00
actions:
Explain new issues workflow and add triage automation Add explanation of how to indicate the new issues workflow to MAINTAINERS.md: triage -> investigation -> devel. The different stages are indicated using Gitlab's scoped labels (mutually exclusive). These stages try to hightlight that the issue cannot be fixed and it's not moving forward because more info is needed, already. Also, add a section to CONTRIBUTING.md highlighting the importance of helping in the triage and investigation stages: developers often cannot fix bugs because lack of time to investigate, but even users that doesn't know how to fix it due to lack of knowledge of the code base can help thanks to their knowledge on networking. Finally, make the 'triage:issues' CI job to work again, adding some new policies with new automations. The automation will add or remove the labels: stale, help-needed::{triage, investigation, devel} and unassigned. The labels help-needed::* and unassigned will be automatically added to all issues without an assignee. This reflects better the reality of not having enough time to work on most of the issues unless there is some external help.
2024-05-23 09:55:52 +00:00
comment: >-
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:
Explain new issues workflow and add triage automation Add explanation of how to indicate the new issues workflow to MAINTAINERS.md: triage -> investigation -> devel. The different stages are indicated using Gitlab's scoped labels (mutually exclusive). These stages try to hightlight that the issue cannot be fixed and it's not moving forward because more info is needed, already. Also, add a section to CONTRIBUTING.md highlighting the importance of helping in the triage and investigation stages: developers often cannot fix bugs because lack of time to investigate, but even users that doesn't know how to fix it due to lack of knowledge of the code base can help thanks to their knowledge on networking. Finally, make the 'triage:issues' CI job to work again, adding some new policies with new automations. The automation will add or remove the labels: stale, help-needed::{triage, investigation, devel} and unassigned. The labels help-needed::* and unassigned will be automatically added to all issues without an assignee. This reflects better the reality of not having enough time to work on most of the issues unless there is some external help.
2024-05-23 09:55:52 +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:
Explain new issues workflow and add triage automation Add explanation of how to indicate the new issues workflow to MAINTAINERS.md: triage -> investigation -> devel. The different stages are indicated using Gitlab's scoped labels (mutually exclusive). These stages try to hightlight that the issue cannot be fixed and it's not moving forward because more info is needed, already. Also, add a section to CONTRIBUTING.md highlighting the importance of helping in the triage and investigation stages: developers often cannot fix bugs because lack of time to investigate, but even users that doesn't know how to fix it due to lack of knowledge of the code base can help thanks to their knowledge on networking. Finally, make the 'triage:issues' CI job to work again, adding some new policies with new automations. The automation will add or remove the labels: stale, help-needed::{triage, investigation, devel} and unassigned. The labels help-needed::* and unassigned will be automatically added to all issues without an assignee. This reflects better the reality of not having enough time to work on most of the issues unless there is some external help.
2024-05-23 09:55:52 +00:00
comment: >-
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:
Explain new issues workflow and add triage automation Add explanation of how to indicate the new issues workflow to MAINTAINERS.md: triage -> investigation -> devel. The different stages are indicated using Gitlab's scoped labels (mutually exclusive). These stages try to hightlight that the issue cannot be fixed and it's not moving forward because more info is needed, already. Also, add a section to CONTRIBUTING.md highlighting the importance of helping in the triage and investigation stages: developers often cannot fix bugs because lack of time to investigate, but even users that doesn't know how to fix it due to lack of knowledge of the code base can help thanks to their knowledge on networking. Finally, make the 'triage:issues' CI job to work again, adding some new policies with new automations. The automation will add or remove the labels: stale, help-needed::{triage, investigation, devel} and unassigned. The labels help-needed::* and unassigned will be automatically added to all issues without an assignee. This reflects better the reality of not having enough time to work on most of the issues unless there is some external help.
2024-05-23 09:55:52 +00:00
- stale
Reference in New Issue Copy Permalink