Skip to content

Locking Resolved Issues/PRs #62623

@RyanCavanaugh

Description

@RyanCavanaugh

Acknowledgement

  • I acknowledge that issues using this template may be closed without further explanation at the maintainer's discretion.

Comment

You may have noticed more locked issues around the repo. The primary reason for this is that we're seeing that most comments on very old and inactive closed issues/PRs tend to fall in certain categories:

  • Users asking unrelated questions; old issues are not a good place to do this. We would prefer they go through the standard triage flow from the beginning
  • Users who are trying to report a regression; these comments typically lack enough information to reproduce the repro, and it's easy for comments like this to accidently go unaddressed. We need all the information from the standard bug form in order to be able to act on these reports.
  • Spam

For transparency, the new rules are:

  • Closed Bugs and Closed/Merged PRs are locked after 6 months of inactivity. This is enough time for a PR to make it into an official release and gather reasonably-timely feedback
  • Questions, Duplicates, and Working as Intended are locked after 2 months of inactivity. Would-be comments here should go back through the primary triage flow in the form of a new issue, or be posted in the linked duplicate issue

As always, feel free to log a new issue if needed. Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    Meta-IssueAn issue about the team, or the direction of TypeScript

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions