- We use weblate to localise this project into many languages. If you are
- unhappy with a translation this is the best start. On how to translate using
- weblate, please see
- [these instructions](https://github.com/louislam/uptime-kuma/blob/master/src/lang/README.md).
-
- There are two cases in which a change cannot be done in weblate and requires a
- PR:
-
- - A text may not be currently localisable. In this case, **adding a new
- language key** via `$t("languageKey")` might be necessary
- - language keys need to be **added to `en.json`** to be visible in weblate. If
- this has not happened, a PR is appreciated.
- - **Adding a new language** requires a new file see
- [these instructions](https://github.com/louislam/uptime-kuma/blob/master/src/lang/README.md)
-
- Because maintainer time is precious, junior maintainers may merge
- uncontroversial PRs in this area.
+ Please add **all** strings that are translatable to `src/lang/en.json`. If translation keys are omitted, they cannot be translated. **Do not include any other languages in your initial pull request** (even if it is your mother tongue) to avoid merge conflicts between Weblate and `master`. Once your PR is merged into `master`, the strings can be translated by awesome people donating their language skills.
+
+ We use Weblate to localise this project into many languages. If you want to help translate Uptime Kuma into your language, please see [these instructions on how to translate using Weblate](https://github.com/louislam/uptime-kuma/blob/master/src/lang/README.md).
+
+ There are some cases where a change cannot be done directly in Weblate and requires a PR:
+
+ - A text may not yet be localisable. In this case, **adding a new language key** via `{{ $t("Translation key") }}` or [`
be sure to **create an empty draft pull request or open an issue, so we can - have a discussion first**. This is especially important for a large pull - request or when you don't know if it will be merged or not. + have a discussion first**. + This is especially important for large pull requests or when you don't know if it will be merged or not. + When adding new features, please also add tests to ensure your changes work as expected and to prevent future regressions. Because of the large impact of this work, only senior maintainers may merge PRs in this area. @@ -219,101 +216,35 @@ to review the appropriate one for your contribution.
--
- ## Steps to Submit a Pull Request
+ Contributing is easy and fun. We will guide you through the process:
- 1. **Fork** the [Uptime-Kuma repository].
-
- [Uptime-Kuma repository]: https://github.com/louislam/uptime-kuma/
-
- 2. **Clone** your forked repository to your local machine.
- 3. **Create a new branch** for your changes (e.g.,
- `feature/add-new-notification-provider-signal`).
- 4. **Initiate a discussion before making major changes** by creating an empty
- commit:
-
- ```sh
- git commit -m "
+ A volunteer maintainer will review your PR as soon as possible.
+ You can help us by reviewing other PRs or taking a look at open issues.
- A **work-in-progress (WIP) PR** must stay in **draft status** until everything
- is finalized.
-
- Since maintainer time is valuable, junior maintainers may merge
- uncontroversial PRs.
-
-