From 67d80f9ae8082d446e2d58227375f5a92eeae933 Mon Sep 17 00:00:00 2001 From: Joey Perrott Date: Thu, 29 Aug 2019 09:29:55 -0700 Subject: [PATCH] docs: create Issue and Pull Request markdown doc, explaining automatic locking policy (#32405) PR Close #32405 --- docs/GITHUB_PROCESS.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 docs/GITHUB_PROCESS.md diff --git a/docs/GITHUB_PROCESS.md b/docs/GITHUB_PROCESS.md new file mode 100644 index 0000000000000..ef031d300cc19 --- /dev/null +++ b/docs/GITHUB_PROCESS.md @@ -0,0 +1,14 @@ + +# 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