Node: Proposal: close all node-v0.x-archive issues with comment

Created on 18 Jun 2017 · 7Comments · Source: nodejs/node

There are still 545 open issues on nodejs/node-v0.x-archive, and they still get discovered and commented on by people.

Also, despite this statement in the README:

New issues and pull requests opened here will automatically be rejected.

, new issues still get opened, and have to be closed manually (example).

Instead of the usual "see a comment, close the issue, recommend they raise a new one in nodejs/node", how about we close all the issues with a stock comment.

Strawman:

This repository is an archive of Node.js before the move to nodejs/node.

If you are still seeing this problem, please raise an issue on nodejs/node.

Most helpful comment

I was originally thinking that this would be a one-time thing, but as it is apparently still possible to open new issues, it might be worth permanently having a bot that replies to all comments and new issues with stock text.

Maybe something for the @nodejs-github-bot (cc/ @nodejs/github-bot )

gibfahn on 18 Jun 2017

👍3

All 7 comments

Maybe something for the @nodejs-github-bot (cc/ @nodejs/github-bot )

gibfahn on 18 Jun 2017

👍3

I'm in favor of this.

cjihrig on 18 Jun 2017

Me too. Would the 'Limit to repository collaborators' option help in stopping people from opening new issues?

Its description is a little vague. What does 'interact' mean exactly? Can people still view issues?

Users that have not been granted push access will be unable to interact with the repository.

bnoordhuis on 19 Jun 2017

I was originally going to suggest the same thing as @bnoordhuis but had the exact same question. We could try going that route and check the old issue tracker from an incognito window (or otherwise not logged in). If the old issues can no longer be seen, we could immediately uncheck the box.

cjihrig on 19 Jun 2017

👍2

I'm +1 on locking the issues in the old repo with a comment directing to the new repo.