feat(workflows): auto-lock closed issues and PRs older than X days

[solracsf]

Summary

Lock Threads is a GitHub Action that locks closed threads (issues, PRs) after a certain (configurable) period of inactivity.

The proposed workflow will search once a week (on sunday) for closed issues and pull requests that have not had any activity in the past 120 days, and lock them to Nextcloud collaborators only (whose can unlock/reopen/comment on them if needed).

This should prevent regular users to comment on old (out-of-date) threads and invite them to open a new issue instead, with up-to-date material.

More info at https://github.com/dessant/lock-threads

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)

[provokateurin]

Blocking for now for internal discussion

[kesselb]

👍

I fear this will create a huge number of notifications, but I like the idea. It happens that people respond to issues and prs that were closed years ago and never receive a response (e.g. because the involved people are not there anymore).

[joshtrichards]

I fear this will create a huge number of notifications, but I like the idea.

@kesselb You mean initially? We could incrementally tweak the options to chunk it. I guess this is one of those "rip the band-aid off things". Or, for the initial batch (existing closed Issues), we could configure to lock w/o comment. As long as the reason is set to resolved, even without adding a comment, it'll look like this (minus the locker name since that doesn't get shown publicly):

Once that's done we can add the explanation comment+lock back in for newly closed Issues going forward.

@solracsf I've thought about doing this. Thanks for taking action and pushing us all to think this through to see if we want to do it.

[susnux]

I would even say an issue (bug report!) which was closed and not marked as stale (thus resolved) be be locked right after closing.
If there is a regression, then a new issue should be created.

[solracsf]

Any news for a Go/no-Go here ?

[provokateurin]

I think we wanted to have this, but I just brought it up in our team chat again to see how we want to proceed.