From 44215271b00a11e6a49b826b09e527d8398332ff Mon Sep 17 00:00:00 2001
From: xinbenlv <zzn-github@zzn.im>
Date: Fri, 23 Jun 2023 09:25:45 -0700
Subject: [PATCH] Add EIP: Linter Scope

Merged by EIP-Bot.
---
 EIPS/eip-7199.md | 33 +++++++++++++++++++++++++++++++++
 1 file changed, 33 insertions(+)
 create mode 100644 EIPS/eip-7199.md

diff --git a/EIPS/eip-7199.md b/EIPS/eip-7199.md
new file mode 100644
index 0000000000000..fda0702e31ae8
--- /dev/null
+++ b/EIPS/eip-7199.md
@@ -0,0 +1,33 @@
+---
+eip: 7199
+title: Linter Scope
+description: Relax the policy for updating EIP.
+author: Zainan Victor Zhou (@xinbenlv)
+discussions-to: https://ethereum-magicians.org/t/proposal-eipw-should-only-complain-about-changing-lines/14762
+status: Draft
+type: Meta
+created: 2023-06-20
+---
+
+## Abstract
+
+Currently in practice EIP linter tools (EIPW, for example) will block a Pull Request for lint errors even if that lint errors was not introduced in that Pull Request.
+This EIP make it explicit that lint errors for untouched lines shall be considered ignoreable except for status change.
+
+## Specification
+
+The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
+
+In an update to an EIP, A Pull Request SHOULD NOT be required to fix linter errors in untouched lines unless it's changing the Status of the EIP.
+
+## Rationale
+
+This policy allows micro contributions for anyone who just want to fix a typo or change a section of a section in a large EIP.
+
+## Security Considerations
+
+None 
+
+## Copyright
+
+Copyright and related rights waived via [CC0](../LICENSE.md).