Skip to content

Proposal to curb amount of open issues on TypeScript project #16637

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jpaulin opened this issue Jun 20, 2017 · 2 comments
Closed

Proposal to curb amount of open issues on TypeScript project #16637

jpaulin opened this issue Jun 20, 2017 · 2 comments
Labels
Question An issue which isn't directly actionable in code

Comments

@jpaulin
Copy link

jpaulin commented Jun 20, 2017

Another project that I've checked quite often, had an bit of issue with a huge amount of
open issues. I'm wondering if TypeScript would benefit, management-wise, from the
automatic curbing of issues that have not received any activity here on Github for
some period of time?

A blog posting on NPM site about automatically curbing open issues

@RyanCavanaugh
Copy link
Member

We already do this (e.g. #16080 (comment) - that is done by a script)

@RyanCavanaugh RyanCavanaugh added the Question An issue which isn't directly actionable in code label Jun 20, 2017
@mhegazy
Copy link
Contributor

mhegazy commented Aug 17, 2017

Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.

@mhegazy mhegazy closed this as completed Aug 17, 2017
@microsoft microsoft locked and limited conversation to collaborators Jun 14, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Question An issue which isn't directly actionable in code
Projects
None yet
Development

No branches or pull requests

3 participants