From 43619fc847e885c375e5119ac7a7305131f071b2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Matias=20Niemel=C3=A4?= Date: Fri, 30 Aug 2019 14:38:07 -0400 Subject: [PATCH] revert: docs: create Issue and Pull Request markdown doc, explaining automatic locking policy (#32405) This reverts commit ad13520b240a83db4097436e5459b890e8193ee4. --- docs/GITHUB_PROCESS.md | 14 -------------- 1 file changed, 14 deletions(-) delete mode 100644 docs/GITHUB_PROCESS.md diff --git a/docs/GITHUB_PROCESS.md b/docs/GITHUB_PROCESS.md deleted file mode 100644 index ef031d300c..0000000000 --- a/docs/GITHUB_PROCESS.md +++ /dev/null @@ -1,14 +0,0 @@ - -# Automatic conversation locking -Closed issues and pull requests are locked automatically after 30 days of inactivity. - -## I want to comment on a locked conversation, what should I do? -When an issue has been closed and inactive for over 30 days, the original context is likely outdated. -If you encounter a similar or related issue in the current version, please open a new issue and -provide up-to-date reproduction instructions. - -## Why lock conversations? -Automatically locking closed, inactive issues guides people towards filing new issues with updated -context rather than commenting on a "resolved" issue that contains out-of-date or unrelated -information. As an example, someone may comment "I'm still having this issue", but without -providing any of the additional information the team needs to investigate. \ No newline at end of file