From 175133ad047264b9f8a2d437f6de685827469da2 Mon Sep 17 00:00:00 2001 From: SkyratBot <59378654+SkyratBot@users.noreply.github.com> Date: Tue, 10 May 2022 02:35:05 +0200 Subject: [PATCH] [MIRROR] Add guidelines to ensure the maintainers and issue jannies understand the place and purpose of templates. [MDB IGNORE] (#13486) * Add guidelines to ensure the maintainers and issue jannies understand the place and purpose of templates. (#66673) Why It's Good For The Game Repo Preemptively preventing a fork threat. * Add guidelines to ensure the maintainers and issue jannies understand the place and purpose of templates. Co-authored-by: Kyle Spier-Swenson --- .github/CONTRIBUTING.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index 3187e212eec..5ddeffadf19 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -64,6 +64,7 @@ These are the few directives we have for project maintainers. - Try to get secondary maintainer approval before merging if you are able to. - PRs with empty commits intended to generate a changelog. - Do not merge PRs that contain content from the [banned content list](./CONTRIBUTING.md#banned-content). +- Do not close PRs purely for breaking a template if the same information is contained without it. These are not steadfast rules as maintainers are expected to use their best judgement when operating. @@ -87,6 +88,7 @@ Things you **CAN** do: Things you **CAN'T** do: * [Close PRs](https://imgur.com/w2RqpX8.png): Only maintainers are allowed to close PRs. Do not hit that button. +* Close issues purely for breaking a template if the same information is contained without it.