@qbittorrent/bug-handlers @qbittorrent/frequent-contributors
I have coded this tool in the past couple days.
It can close old issues, leave a comment, apply a label, lock the issue and skip issues with certain labels.
After I apply my other tool mentioned in #12101 I intend to run this tool on the repo with the following arguments:
--cutoff-timepoint=2019-05-06T00:00:00Z --apply-label="autoCloseOldIssue" --skip-label="Feature request" --comment="This issue is automatically closed for being very old with no activity.\nIf you still experience it with the latest qBittorrent version then feel free to open a new issue." --lock
I chose 2019-05-06T00:00:00Z semi-randomly. It is the day after the v4.1.6 release which was about 1 year ago. I figured that all those issues can be closed instantly.
PS: This will not close issues that were updated after that timepoint. eg by someone leaving a comment, applying a label etc.
A dry-run of the above cmdline shows that 819 will be closed.
Second Phase
After the above procedure, I plan the following for all issues between v4.1.6 and v4.2.0:
Non updated issues till today, will be marked with a label
A comment will be left, informing users for the imminent issue closing
After 10-15 days, the marked ones will be rechecked. If no activity was present they will be autoclosed and locked
Do you have any comments on the above before I proceed?
@qbittorrent/bug-handlers @qbittorrent/frequent-contributors I have coded this tool in the past couple days.
It can close old issues, leave a comment, apply a label, lock the issue and skip issues with certain labels.
After I apply my other tool mentioned in #12101 I intend to run this tool on the repo with the following arguments:
I chose
2019-05-06T00:00:00Z
semi-randomly. It is the day after the v4.1.6 release which was about 1 year ago. I figured that all those issues can be closed instantly. PS: This will not close issues that were updated after that timepoint. eg by someone leaving a comment, applying a label etc.A dry-run of the above cmdline shows that 819 will be closed.
Second Phase
After the above procedure, I plan the following for all issues between v4.1.6 and v4.2.0:
Do you have any comments on the above before I proceed?