Просмотр исходного кода

Clarify PR guidelines for translation contributions

Emphasize the importance of standalone PRs for translation updates.
Classic298 4 месяцев назад
Родитель
Сommit
ab07bab140
1 измененных файлов с 3 добавлено и 0 удалено
  1. 3 0
      docs/CONTRIBUTING.md

+ 3 - 0
docs/CONTRIBUTING.md

@@ -74,6 +74,9 @@ To add a new language:
 - Copy the American English translation file(s) (from `en-US` directory in `src/lib/i18n/locale`) to this new directory and update the string values in JSON format according to your language. Make sure to preserve the structure of the JSON object.
 - Copy the American English translation file(s) (from `en-US` directory in `src/lib/i18n/locale`) to this new directory and update the string values in JSON format according to your language. Make sure to preserve the structure of the JSON object.
 - Add the language code and its respective title to languages file at `src/lib/i18n/locales/languages.json`.
 - Add the language code and its respective title to languages file at `src/lib/i18n/locales/languages.json`.
 
 
+> [!NOTE]
+> When adding new translations, do so in a standalone PR! Feature PRs or PRs fixing a bug should not contain translation updates. Always keep the scope of a PR narrow.
+
 ### 🤔 Questions & Feedback
 ### 🤔 Questions & Feedback
 
 
 Got questions or feedback? Join our [Discord community](https://discord.gg/5rJgQTnV4s) or open an issue or discussion. We're here to help!
 Got questions or feedback? Join our [Discord community](https://discord.gg/5rJgQTnV4s) or open an issue or discussion. We're here to help!