You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These files are managed by a dedicated localization team through a separate workflow.
8
+
9
+
## Absolute Prohibitions - You MUST NOT:
10
+
11
+
- ❌ NEVER suggest translating English text to other languages
12
+
- ❌ NEVER comment that text should be translated to match the locale
13
+
- ❌ NEVER suggest alternative translations or phrasings in any language
14
+
- ❌ NEVER comment on language consistency (e.g., "this should be in Arabic")
15
+
- ❌ NEVER suggest changing text content for localization purposes
16
+
- ❌ NEVER comment on which language should be used
17
+
- ❌ NEVER suggest adding or removing message keys
18
+
- ❌ NEVER provide language-specific style recommendations
19
+
20
+
## Why These Files Are Off-Limits:
21
+
22
+
Translation suggestions make PR pages UNRESPONSIVE and overwhelm human reviewers. The localization team handles all translation work through a separate quality assurance process.
23
+
24
+
## The ONLY Acceptable Comments:
25
+
26
+
✅ Critical JSON syntax errors that would break the build (missing commas, unclosed brackets)
27
+
✅ Severe grammar errors (ONLY if they would cause user confusion)
28
+
29
+
## Examples of FORBIDDEN Comments:
30
+
31
+
- ❌ "This English text should be translated to Arabic"
32
+
- ❌ "Translation is missing for this locale"
33
+
- ❌ "Consider translating '(No subject)' to '(بدون موضوع)'"
34
+
- ❌ "This text is in English but should be in German"
35
+
- ❌ "Inconsistent language - use native translation"
36
+
37
+
If you have ANY doubt about whether to comment on a localization file, DO NOT COMMENT.
text: 'Files attached in a very long message: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed vel tempus orci, sit amet tempor tortor. Etiam ut aliquam nisi.',
0 commit comments