From 0d9b978c1e29965fbce3a28b89a89371c0123c7d Mon Sep 17 00:00:00 2001 From: camperbot Date: Wed, 27 Dec 2023 21:01:57 +0530 Subject: [PATCH] chore(i18n,docs): processed translations (#52650) --- .../how-to-open-a-pull-request.md | 17 +++--- .../chinese-traditional/moderator-handbook.md | 6 +- .../chinese-traditional/reply-templates.md | 16 +++++- .../chinese/how-to-open-a-pull-request.md | 17 +++--- docs/i18n/chinese/moderator-handbook.md | 6 +- docs/i18n/chinese/reply-templates.md | 16 +++++- .../espanol/how-to-open-a-pull-request.md | 17 +++--- docs/i18n/espanol/moderator-handbook.md | 6 +- docs/i18n/espanol/reply-templates.md | 16 +++++- .../i18n/german/how-to-open-a-pull-request.md | 17 +++--- docs/i18n/german/moderator-handbook.md | 6 +- docs/i18n/german/reply-templates.md | 16 +++++- .../italian/how-to-open-a-pull-request.md | 17 +++--- docs/i18n/italian/moderator-handbook.md | 6 +- docs/i18n/italian/reply-templates.md | 16 +++++- .../japanese/how-to-open-a-pull-request.md | 17 +++--- docs/i18n/japanese/moderator-handbook.md | 6 +- docs/i18n/japanese/reply-templates.md | 16 +++++- .../portuguese/how-to-open-a-pull-request.md | 17 +++--- docs/i18n/portuguese/moderator-handbook.md | 6 +- docs/i18n/portuguese/reply-templates.md | 16 +++++- .../ukrainian/how-to-open-a-pull-request.md | 17 +++--- .../how-to-work-on-coding-challenges.md | 56 +++++++++---------- .../how-to-work-on-localized-client-webapp.md | 6 +- docs/i18n/ukrainian/moderator-handbook.md | 6 +- docs/i18n/ukrainian/reply-templates.md | 16 +++++- .../troubleshooting-development-issues.md | 2 +- 27 files changed, 240 insertions(+), 136 deletions(-) diff --git a/docs/i18n/chinese-traditional/how-to-open-a-pull-request.md b/docs/i18n/chinese-traditional/how-to-open-a-pull-request.md index 4cd62933460..af4687ce43b 100644 --- a/docs/i18n/chinese-traditional/how-to-open-a-pull-request.md +++ b/docs/i18n/chinese-traditional/how-to-open-a-pull-request.md @@ -7,19 +7,20 @@ We expect our contributors to be aware of the process specific to this project. Some examples of this are: 1. Do not edit files directly through GitHub – while you can, it's not a good idea. -2. Make sure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. -3. Use the correct way to link issues in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like. -4. Do not "@mention" or request someone for reviews too many times. +2. Make sure the PR title follows [our convention](#prepare-a-good-pr-title). +3. Make sure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. +4. Use the correct way to link issues in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like. +5. Do not "@mention" or request someone for reviews too many times. We understand you are excited about contributing. As much as a maintainer will love to get back to you, they are busy people looking after hundreds of requests just like yours. Be patient, someone will get to you sooner or later. -5. Do not work directly off your `main` branch - create a new branch for the changes you are working on. +6. Do not work directly off your `main` branch - create a new branch for the changes you are working on. > [!NOTE] Your PR should be targeting changes to the English curriculum only. Read [this guide](index.md#translations) instead for contributing to translations. ## Prepare a Good PR Title -We recommend using [conventional title and messages](https://www.conventionalcommits.org/) for commits and pull request. The convention has the following format: +We use [conventional title and messages](https://www.conventionalcommits.org/) for commits and pull requests. The convention has the following format: > `([optional scope(s)]): ` > @@ -27,7 +28,7 @@ We recommend using [conventional title and messages](https://www.conventionalcom > > `fix(learn): tests for the do...while loop challenge` -Whenever you open a Pull Request(PR), you can use the below to determine the type, scope (optional), and description. +Whenever you open a Pull Request (PR), you can use the below to determine the type, scope (optional), and description. **Type:** @@ -81,7 +82,7 @@ Some examples of good PR titles would be: - You will be presented with a pull request template. This is a checklist that you should have followed before opening the pull request. - - Fill in the details as you see fit. This information will be reviewed and the reviewers will decide whether or not your pull request is accepted. + - Fill in the details as you see fit. Ensure that you give the reviewers enough context to review the changes. If the PR makes changes to the UI, be sure to include screenshots of the changes as well. All of this information will be reviewed and the reviewers will decide whether or not your pull request is accepted. - If the PR is meant to address an existing GitHub Issue then, at the end of your PR's description body, use the keyword _Closes_ with the issue number to [automatically close that issue if the PR is accepted and merged](https://help.github.com/en/articles/closing-issues-using-keywords). @@ -91,7 +92,7 @@ Some examples of good PR titles would be: - This is very important when making changes that are not just edits to text content like documentation or a challenge description. Examples of changes that need local testing include JavaScript, CSS, or HTML, which could change the functionality or layout of a page. - - If your PR affects the behaviour of a page, it should be accompanied by corresponding [Cypress integration tests](how-to-add-cypress-tests.md). + - If your PR affects the behavior of a page, it should be accompanied by corresponding [Playwright integration tests](how-to-add-playwright-tests.md). ## Feedback on Pull Requests diff --git a/docs/i18n/chinese-traditional/moderator-handbook.md b/docs/i18n/chinese-traditional/moderator-handbook.md index bbefc6d8b99..e00a773c167 100644 --- a/docs/i18n/chinese-traditional/moderator-handbook.md +++ b/docs/i18n/chinese-traditional/moderator-handbook.md @@ -201,7 +201,7 @@ If a user creates a thread asking for feedback on a solution, move the thread to ### Underage Users -Our [Terms of Service](https://freecodecamp.org/terms) require that freeCodeCamp users be at least 13 years of age. If a user reveals that they are under the age of 13, send them the message (below), suspend the account then **Email `support[at]freecodecamp.org` to delete the user's freeCodeCamp /learn and forum accounts as well (providing a link to the offending forum account).** +Our [Terms of Service](https://freecodecamp.org/terms) require that freeCodeCamp users be at least 13 years of age. If a user reveals that they are under the age of 13, send them the message below, suspend their account, then email the link of their forum account to `support[at]freecodecamp.org` for their freeCodeCamp /learn and forum accounts removal. ```markdown SUBJECT: Users under 13 are not allowed to use the forum per our Terms of Service. @@ -243,7 +243,7 @@ Here's how moderators deal with violations of our [Code of Conduct](https://code For minor offences, a warning may be issued with the `/warn` command. For more egregious offences, you can remove the member from the server temporarily with the `/kick` command, or permanently with the `/ban` command. In some cases, a member may just need some time to cool off and collect their thoughts - the `/mute` command allows you to prevent them from engaging with our community for a set period of time. A muted member can see the conversation, but cannot post messages or add reactions. - All moderation commands will take a `reason` parameter, which should be a short explanation of why the action was taken. Moderation actions done with the bot will be logged in `#mod-log`, which allows us all to stay on the same page. As such, we should avoid using Discord's built-in moderation tools, as they will not be logged. + All moderation commands will take a `reason` parameter, which should be a short explanation of why the action was taken. Moderation actions done with the bot will be logged in `#mod-actions`, which allows us all to stay on the same page. As such, we should avoid using Discord's built-in moderation tools, as they will not be logged. > [!WARNING] The reason provided to a moderation command will also be included in the DM notification to the camper. Please remember to be professional here. @@ -257,7 +257,7 @@ Here's how moderators deal with violations of our [Code of Conduct](https://code 4. **Deleting messages** - Our moderation bot is configured to log deleted messages automatically in the `#mod-log` channel. If a message is not in line with our Code of Conduct, or otherwise not appropriate for our community, you are generally safe to delete it. + Our moderation bot is configured to log deleted messages automatically in the `#mod-actions` channel. If a message is not in line with our Code of Conduct, or otherwise not appropriate for our community, you are generally safe to delete it. Note that if the message contains content that violates Discord's terms of service, you'll want to report it via https://dis.gd/report **prior to** deleting it. diff --git a/docs/i18n/chinese-traditional/reply-templates.md b/docs/i18n/chinese-traditional/reply-templates.md index d5c5110346b..c9632e049b6 100644 --- a/docs/i18n/chinese-traditional/reply-templates.md +++ b/docs/i18n/chinese-traditional/reply-templates.md @@ -107,7 +107,7 @@ If you have any questions, feel free to ask questions on the ["Contributors" cat > When PR is invalid. ```markdown -Hey @username +Hey there, Thank you for opening this pull request. @@ -157,7 +157,7 @@ Thank you for your enthusiasm in contributing to our project. We eagerly await m **Happy Contributing!** 🌟 ``` -## Issue Not Triaged +## PR Opened While Issue Is Not Triaged > When a PR is opened for an issue that hasn't been triaged and marked as ready for contribution. @@ -234,3 +234,15 @@ Issues labeled with `help wanted` or `first timers only` are open for contributi Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you. ``` + +## Requests for Assignment While Issue Is Not Triaged + +> When a contributor requests for assignment but the issue hasn't been triaged or marked as ready for contribution. + +```md +Hi there, + +Thanks for your interest in contributing. + +This issue has not been triaged yet, and a solution has not been agreed upon. Once the issue is open for contribution, you are welcome to create a pull request to reflect the issue consensus. Please also note that we typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. +``` \ No newline at end of file diff --git a/docs/i18n/chinese/how-to-open-a-pull-request.md b/docs/i18n/chinese/how-to-open-a-pull-request.md index 4cd62933460..af4687ce43b 100644 --- a/docs/i18n/chinese/how-to-open-a-pull-request.md +++ b/docs/i18n/chinese/how-to-open-a-pull-request.md @@ -7,19 +7,20 @@ We expect our contributors to be aware of the process specific to this project. Some examples of this are: 1. Do not edit files directly through GitHub – while you can, it's not a good idea. -2. Make sure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. -3. Use the correct way to link issues in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like. -4. Do not "@mention" or request someone for reviews too many times. +2. Make sure the PR title follows [our convention](#prepare-a-good-pr-title). +3. Make sure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. +4. Use the correct way to link issues in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like. +5. Do not "@mention" or request someone for reviews too many times. We understand you are excited about contributing. As much as a maintainer will love to get back to you, they are busy people looking after hundreds of requests just like yours. Be patient, someone will get to you sooner or later. -5. Do not work directly off your `main` branch - create a new branch for the changes you are working on. +6. Do not work directly off your `main` branch - create a new branch for the changes you are working on. > [!NOTE] Your PR should be targeting changes to the English curriculum only. Read [this guide](index.md#translations) instead for contributing to translations. ## Prepare a Good PR Title -We recommend using [conventional title and messages](https://www.conventionalcommits.org/) for commits and pull request. The convention has the following format: +We use [conventional title and messages](https://www.conventionalcommits.org/) for commits and pull requests. The convention has the following format: > `([optional scope(s)]): ` > @@ -27,7 +28,7 @@ We recommend using [conventional title and messages](https://www.conventionalcom > > `fix(learn): tests for the do...while loop challenge` -Whenever you open a Pull Request(PR), you can use the below to determine the type, scope (optional), and description. +Whenever you open a Pull Request (PR), you can use the below to determine the type, scope (optional), and description. **Type:** @@ -81,7 +82,7 @@ Some examples of good PR titles would be: - You will be presented with a pull request template. This is a checklist that you should have followed before opening the pull request. - - Fill in the details as you see fit. This information will be reviewed and the reviewers will decide whether or not your pull request is accepted. + - Fill in the details as you see fit. Ensure that you give the reviewers enough context to review the changes. If the PR makes changes to the UI, be sure to include screenshots of the changes as well. All of this information will be reviewed and the reviewers will decide whether or not your pull request is accepted. - If the PR is meant to address an existing GitHub Issue then, at the end of your PR's description body, use the keyword _Closes_ with the issue number to [automatically close that issue if the PR is accepted and merged](https://help.github.com/en/articles/closing-issues-using-keywords). @@ -91,7 +92,7 @@ Some examples of good PR titles would be: - This is very important when making changes that are not just edits to text content like documentation or a challenge description. Examples of changes that need local testing include JavaScript, CSS, or HTML, which could change the functionality or layout of a page. - - If your PR affects the behaviour of a page, it should be accompanied by corresponding [Cypress integration tests](how-to-add-cypress-tests.md). + - If your PR affects the behavior of a page, it should be accompanied by corresponding [Playwright integration tests](how-to-add-playwright-tests.md). ## Feedback on Pull Requests diff --git a/docs/i18n/chinese/moderator-handbook.md b/docs/i18n/chinese/moderator-handbook.md index b648f5d6a4a..6b79723784a 100644 --- a/docs/i18n/chinese/moderator-handbook.md +++ b/docs/i18n/chinese/moderator-handbook.md @@ -201,7 +201,7 @@ If a user creates a thread asking for feedback on a solution, move the thread to ### Underage Users -Our [Terms of Service](https://freecodecamp.org/terms) require that freeCodeCamp users be at least 13 years of age. If a user reveals that they are under the age of 13, send them the message (below), suspend the account then **Email `support[at]freecodecamp.org` to delete the user's freeCodeCamp /learn and forum accounts as well (providing a link to the offending forum account).** +Our [Terms of Service](https://freecodecamp.org/terms) require that freeCodeCamp users be at least 13 years of age. If a user reveals that they are under the age of 13, send them the message below, suspend their account, then email the link of their forum account to `support[at]freecodecamp.org` for their freeCodeCamp /learn and forum accounts removal. ```markdown SUBJECT: Users under 13 are not allowed to use the forum per our Terms of Service. @@ -243,7 +243,7 @@ Here's how moderators deal with violations of our [Code of Conduct](https://code For minor offences, a warning may be issued with the `/warn` command. For more egregious offences, you can remove the member from the server temporarily with the `/kick` command, or permanently with the `/ban` command. In some cases, a member may just need some time to cool off and collect their thoughts - the `/mute` command allows you to prevent them from engaging with our community for a set period of time. A muted member can see the conversation, but cannot post messages or add reactions. - All moderation commands will take a `reason` parameter, which should be a short explanation of why the action was taken. Moderation actions done with the bot will be logged in `#mod-log`, which allows us all to stay on the same page. As such, we should avoid using Discord's built-in moderation tools, as they will not be logged. + All moderation commands will take a `reason` parameter, which should be a short explanation of why the action was taken. Moderation actions done with the bot will be logged in `#mod-actions`, which allows us all to stay on the same page. As such, we should avoid using Discord's built-in moderation tools, as they will not be logged. > [!WARNING] The reason provided to a moderation command will also be included in the DM notification to the camper. Please remember to be professional here. @@ -257,7 +257,7 @@ Here's how moderators deal with violations of our [Code of Conduct](https://code 4. **Deleting messages** - Our moderation bot is configured to log deleted messages automatically in the `#mod-log` channel. If a message is not in line with our Code of Conduct, or otherwise not appropriate for our community, you are generally safe to delete it. + Our moderation bot is configured to log deleted messages automatically in the `#mod-actions` channel. If a message is not in line with our Code of Conduct, or otherwise not appropriate for our community, you are generally safe to delete it. Note that if the message contains content that violates Discord's terms of service, you'll want to report it via https://dis.gd/report **prior to** deleting it. diff --git a/docs/i18n/chinese/reply-templates.md b/docs/i18n/chinese/reply-templates.md index d5c5110346b..c9632e049b6 100644 --- a/docs/i18n/chinese/reply-templates.md +++ b/docs/i18n/chinese/reply-templates.md @@ -107,7 +107,7 @@ If you have any questions, feel free to ask questions on the ["Contributors" cat > When PR is invalid. ```markdown -Hey @username +Hey there, Thank you for opening this pull request. @@ -157,7 +157,7 @@ Thank you for your enthusiasm in contributing to our project. We eagerly await m **Happy Contributing!** 🌟 ``` -## Issue Not Triaged +## PR Opened While Issue Is Not Triaged > When a PR is opened for an issue that hasn't been triaged and marked as ready for contribution. @@ -234,3 +234,15 @@ Issues labeled with `help wanted` or `first timers only` are open for contributi Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you. ``` + +## Requests for Assignment While Issue Is Not Triaged + +> When a contributor requests for assignment but the issue hasn't been triaged or marked as ready for contribution. + +```md +Hi there, + +Thanks for your interest in contributing. + +This issue has not been triaged yet, and a solution has not been agreed upon. Once the issue is open for contribution, you are welcome to create a pull request to reflect the issue consensus. Please also note that we typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. +``` \ No newline at end of file diff --git a/docs/i18n/espanol/how-to-open-a-pull-request.md b/docs/i18n/espanol/how-to-open-a-pull-request.md index 2c876dda660..083a8231eba 100644 --- a/docs/i18n/espanol/how-to-open-a-pull-request.md +++ b/docs/i18n/espanol/how-to-open-a-pull-request.md @@ -7,19 +7,20 @@ Esperamos que nuestros colaboradores conozcan el proceso específico de este pro Algunos ejemplos de ello son: 1. No edite archivos directamente a través de GitHub – mientras pueda, no es una buena idea. -2. Asegúrate de seguir la lista de PR y no solo marcar las cosas; de lo contrario, no te tomaremos en serio. -3. Utilice la forma correcta de vincular problemas en la descripción del PR actualizando el `XXXXX`. No solo añada números de emisión en cualquier lugar y donde le plazca. -4. No usar "@mention" o solicitar comentarios demasiadas veces. +2. Make sure the PR title follows [our convention](#prepare-a-good-pr-title). +3. Asegúrate de seguir la lista de PR y no solo marcar las cosas; de lo contrario, no te tomaremos en serio. +4. Utilice la forma correcta de vincular problemas en la descripción del PR actualizando el `XXXXX`. No solo añada números de emisión en cualquier lugar y donde le plazca. +5. No usar "@mention" o solicitar comentarios demasiadas veces. Entendemos que está emocionado por contribuir. As much as a maintainer will love to get back to you, they are busy people looking after hundreds of requests just like yours. Be patient, someone will get to you sooner or later. -5. Do not work directly off your `main` branch - create a new branch for the changes you are working on. +6. Do not work directly off your `main` branch - create a new branch for the changes you are working on. > [!NOTE] Your PR should be targeting changes to the English curriculum only. Read [this guide](index.md#translations) instead for contributing to translations. ## Prepare a Good PR Title -We recommend using [conventional title and messages](https://www.conventionalcommits.org/) for commits and pull request. The convention has the following format: +We use [conventional title and messages](https://www.conventionalcommits.org/) for commits and pull requests. The convention has the following format: > `([ámbito opcional]): ` > @@ -27,7 +28,7 @@ We recommend using [conventional title and messages](https://www.conventionalcom > > `fix(learn): tests for the do...while loop challenge` -Whenever you open a Pull Request(PR), you can use the below to determine the type, scope (optional), and description. +Whenever you open a Pull Request (PR), you can use the below to determine the type, scope (optional), and description. **Type:** @@ -81,7 +82,7 @@ Some examples of good PR titles would be: - Se le presentará una plantilla de pull request. Esta es una lista de verificación que debería haber seguido antes de abrir la solicitud de pull request. - - Rellene los detalles como considere oportuno. Esta información será revisada y los revisores decidirán si su pull request es o no aceptada. + - Rellene los detalles como considere oportuno. Ensure that you give the reviewers enough context to review the changes. If the PR makes changes to the UI, be sure to include screenshots of the changes as well. All of this information will be reviewed and the reviewers will decide whether or not your pull request is accepted. - Si el PR está pensado para abordar un problema existente de GitHub entonces, al final de el cuerpo de la descripción de su PR, use la palabra clave _Cierra_ con el número de incidencia para [cerrar automáticamente ese problema si se acepta y fusionan las relaciones públicas](https://help.github.com/en/articles/closing-issues-using-keywords). @@ -91,7 +92,7 @@ Some examples of good PR titles would be: - Esto es muy importante cuando se hagan cambios que no sean solo ediciones del contenido de texto como documentación o una descripción de un desafío. Examples of changes that need local testing include JavaScript, CSS, or HTML, which could change the functionality or layout of a page. - - If your PR affects the behaviour of a page, it should be accompanied by corresponding [Cypress integration tests](how-to-add-cypress-tests.md). + - If your PR affects the behavior of a page, it should be accompanied by corresponding [Playwright integration tests](how-to-add-playwright-tests.md). ## Feedback on Pull Requests diff --git a/docs/i18n/espanol/moderator-handbook.md b/docs/i18n/espanol/moderator-handbook.md index af77665e62c..9d092f19be5 100644 --- a/docs/i18n/espanol/moderator-handbook.md +++ b/docs/i18n/espanol/moderator-handbook.md @@ -201,7 +201,7 @@ If a user creates a thread asking for feedback on a solution, move the thread to ### Underage Users -Our [Terms of Service](https://freecodecamp.org/terms) require that freeCodeCamp users be at least 13 years of age. If a user reveals that they are under the age of 13, send them the message (below), suspend the account then **Email `support[at]freecodecamp.org` to delete the user's freeCodeCamp /learn and forum accounts as well (providing a link to the offending forum account).** +Our [Terms of Service](https://freecodecamp.org/terms) require that freeCodeCamp users be at least 13 years of age. If a user reveals that they are under the age of 13, send them the message below, suspend their account, then email the link of their forum account to `support[at]freecodecamp.org` for their freeCodeCamp /learn and forum accounts removal. ```markdown SUBJECT: Los usuarios menores de 13 años no pueden utilizar el foro según nuestras Condiciones de Servicio. @@ -243,7 +243,7 @@ Here's how moderators deal with violations of our [Code of Conduct](https://code For minor offences, a warning may be issued with the `/warn` command. For more egregious offences, you can remove the member from the server temporarily with the `/kick` command, or permanently with the `/ban` command. In some cases, a member may just need some time to cool off and collect their thoughts - the `/mute` command allows you to prevent them from engaging with our community for a set period of time. A muted member can see the conversation, but cannot post messages or add reactions. - All moderation commands will take a `reason` parameter, which should be a short explanation of why the action was taken. Moderation actions done with the bot will be logged in `#mod-log`, which allows us all to stay on the same page. As such, we should avoid using Discord's built-in moderation tools, as they will not be logged. + All moderation commands will take a `reason` parameter, which should be a short explanation of why the action was taken. Moderation actions done with the bot will be logged in `#mod-actions`, which allows us all to stay on the same page. As such, we should avoid using Discord's built-in moderation tools, as they will not be logged. > [!WARNING] The reason provided to a moderation command will also be included in the DM notification to the camper. Please remember to be professional here. @@ -257,7 +257,7 @@ Here's how moderators deal with violations of our [Code of Conduct](https://code 4. **Deleting messages** - Our moderation bot is configured to log deleted messages automatically in the `#mod-log` channel. If a message is not in line with our Code of Conduct, or otherwise not appropriate for our community, you are generally safe to delete it. + Our moderation bot is configured to log deleted messages automatically in the `#mod-actions` channel. If a message is not in line with our Code of Conduct, or otherwise not appropriate for our community, you are generally safe to delete it. Note that if the message contains content that violates Discord's terms of service, you'll want to report it via https://dis.gd/report **prior to** deleting it. diff --git a/docs/i18n/espanol/reply-templates.md b/docs/i18n/espanol/reply-templates.md index d5c5110346b..c9632e049b6 100644 --- a/docs/i18n/espanol/reply-templates.md +++ b/docs/i18n/espanol/reply-templates.md @@ -107,7 +107,7 @@ If you have any questions, feel free to ask questions on the ["Contributors" cat > When PR is invalid. ```markdown -Hey @username +Hey there, Thank you for opening this pull request. @@ -157,7 +157,7 @@ Thank you for your enthusiasm in contributing to our project. We eagerly await m **Happy Contributing!** 🌟 ``` -## Issue Not Triaged +## PR Opened While Issue Is Not Triaged > When a PR is opened for an issue that hasn't been triaged and marked as ready for contribution. @@ -234,3 +234,15 @@ Issues labeled with `help wanted` or `first timers only` are open for contributi Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you. ``` + +## Requests for Assignment While Issue Is Not Triaged + +> When a contributor requests for assignment but the issue hasn't been triaged or marked as ready for contribution. + +```md +Hi there, + +Thanks for your interest in contributing. + +This issue has not been triaged yet, and a solution has not been agreed upon. Once the issue is open for contribution, you are welcome to create a pull request to reflect the issue consensus. Please also note that we typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. +``` \ No newline at end of file diff --git a/docs/i18n/german/how-to-open-a-pull-request.md b/docs/i18n/german/how-to-open-a-pull-request.md index c18bec158f4..63a775d5752 100644 --- a/docs/i18n/german/how-to-open-a-pull-request.md +++ b/docs/i18n/german/how-to-open-a-pull-request.md @@ -7,19 +7,20 @@ Wir erwarten von unseren Mitwirkenden, dass sie den für dieses Projekt spezifis Einige Beispiele hierfür sind: 1. Bearbeite Dateien nicht direkt über GitHub - Das kannst du zwar, aber es ist keine gute Idee. -2. Achte darauf, dass du die PR-Checkliste befolgst und nicht nur Dinge abhakst, sonst nehmen wir dich nicht ernst. -3. Verwende die korrekte Art der Verknüpfung von Themen in der Beschreibung des PR, indem du die `XXXXXX` aktualisierst. Füge nicht einfach überall und nach Lust und Laune Heftnummern ein. -4. Erwähne jemanden nicht zu oft mit "@mention" oder bitte ihn nicht zu oft um Bewertungen. +2. Make sure the PR title follows [our convention](#prepare-a-good-pr-title). +3. Achte darauf, dass du die PR-Checkliste befolgst und nicht nur Dinge abhakst, sonst nehmen wir dich nicht ernst. +4. Verwende die korrekte Art der Verknüpfung von Themen in der Beschreibung des PR, indem du die `XXXXXX` aktualisierst. Füge nicht einfach überall und nach Lust und Laune Heftnummern ein. +5. Erwähne jemanden nicht zu oft mit "@mention" oder bitte ihn nicht zu oft um Bewertungen. Wir verstehen, dass du gerne einen Beitrag leisten möchtest. So gerne sich ein Betreuer auch bei dir melden würde, er hat alle Hände voll zu tun, um Hunderte von Anfragen wie deine zu bearbeiten. Habe Geduld, früher oder später wird sich jemand bei dir melden. -5. Arbeite nicht direkt an deinem `Hauptzweig` - erstelle einen neuen Zweig für die Änderungen, an denen du arbeitest. +6. Arbeite nicht direkt an deinem `Hauptzweig` - erstelle einen neuen Zweig für die Änderungen, an denen du arbeitest. > [!NOTE] Deine Öffentlichkeitsarbeit sollte sich nur auf Änderungen des englischen Lehrplans beziehen. Lese stattdessen [diesen Leitfaden](index.md#translations), um zu Übersetzungen beizutragen. ## Prepare a Good PR Title -Wir empfehlen, [konventionelle Titel und Nachrichten](https://www.conventionalcommits.org/) für Commits und Pull Requests zu verwenden. Die Konvention hat das folgende Format: +We use [conventional title and messages](https://www.conventionalcommits.org/) for commits and pull requests. Die Konvention hat das folgende Format: > `([optional scope(s)]): ` > @@ -27,7 +28,7 @@ Wir empfehlen, [konventionelle Titel und Nachrichten](https://www.conventionalco > > `fix(learn): tests for the do...while loop challenge` -Wenn du einen Pull Request (PR) öffnest, kannst du den Typ, den Geltungsbereich (optional) und die Beschreibung festlegen. +Whenever you open a Pull Request (PR), you can use the below to determine the type, scope (optional), and description. **Typ:** @@ -81,7 +82,7 @@ Einige Beispiele für gute PR-Titel wären: - Du erhältst eine Vorlage für einen Pull-Request. Dies ist eine Checkliste, die du befolgen solltest, bevor du den Pull-Request öffnest. - - Fülle die Details so aus, wie du es für richtig hältst. Diese Informationen werden geprüft und die Prüfer entscheiden, ob dein Pull-Request angenommen wird oder nicht. + - Fülle die Details so aus, wie du es für richtig hältst. Ensure that you give the reviewers enough context to review the changes. If the PR makes changes to the UI, be sure to include screenshots of the changes as well. All of this information will be reviewed and the reviewers will decide whether or not your pull request is accepted. - Wenn der PR ein bestehendes GitHub Problem beheben soll, dann am Ende von der Beschreibungstext deines PR verwenden Sie das Schlüsselwort _Schließt_ mit der Ticketnummer zu [automatisch schließen, wenn der PR akzeptiert und zusammengeführt wird](https://help.github.com/en/articles/closing-issues-using-keywords). @@ -91,7 +92,7 @@ Einige Beispiele für gute PR-Titel wären: - Das ist sehr wichtig, wenn du Änderungen vornimmst, die nicht nur Textinhalte wie die Dokumentation oder eine Aufgabenbeschreibung betreffen. Examples of changes that need local testing include JavaScript, CSS, or HTML, which could change the functionality or layout of a page. - - If your PR affects the behaviour of a page, it should be accompanied by corresponding [Cypress integration tests](how-to-add-cypress-tests.md). + - If your PR affects the behavior of a page, it should be accompanied by corresponding [Playwright integration tests](how-to-add-playwright-tests.md). ## Feedback on Pull Requests diff --git a/docs/i18n/german/moderator-handbook.md b/docs/i18n/german/moderator-handbook.md index 3037b20aad0..f94c90dc0a9 100644 --- a/docs/i18n/german/moderator-handbook.md +++ b/docs/i18n/german/moderator-handbook.md @@ -201,7 +201,7 @@ If a user creates a thread asking for feedback on a solution, move the thread to ### Underage Users -Our [Terms of Service](https://freecodecamp.org/terms) require that freeCodeCamp users be at least 13 years of age. If a user reveals that they are under the age of 13, send them the message (below), suspend the account then **Email `support[at]freecodecamp.org` to delete the user's freeCodeCamp /learn and forum accounts as well (providing a link to the offending forum account).** +Our [Terms of Service](https://freecodecamp.org/terms) require that freeCodeCamp users be at least 13 years of age. If a user reveals that they are under the age of 13, send them the message below, suspend their account, then email the link of their forum account to `support[at]freecodecamp.org` for their freeCodeCamp /learn and forum accounts removal. ```markdown SUBJECT: Users under 13 are not allowed to use the forum per our Terms of Service. @@ -243,7 +243,7 @@ Here's how moderators deal with violations of our [Code of Conduct](https://code For minor offences, a warning may be issued with the `/warn` command. For more egregious offences, you can remove the member from the server temporarily with the `/kick` command, or permanently with the `/ban` command. In some cases, a member may just need some time to cool off and collect their thoughts - the `/mute` command allows you to prevent them from engaging with our community for a set period of time. A muted member can see the conversation, but cannot post messages or add reactions. - All moderation commands will take a `reason` parameter, which should be a short explanation of why the action was taken. Moderation actions done with the bot will be logged in `#mod-log`, which allows us all to stay on the same page. As such, we should avoid using Discord's built-in moderation tools, as they will not be logged. + All moderation commands will take a `reason` parameter, which should be a short explanation of why the action was taken. Moderation actions done with the bot will be logged in `#mod-actions`, which allows us all to stay on the same page. As such, we should avoid using Discord's built-in moderation tools, as they will not be logged. > [!WARNING] The reason provided to a moderation command will also be included in the DM notification to the camper. Please remember to be professional here. @@ -257,7 +257,7 @@ Here's how moderators deal with violations of our [Code of Conduct](https://code 4. **Deleting messages** - Our moderation bot is configured to log deleted messages automatically in the `#mod-log` channel. If a message is not in line with our Code of Conduct, or otherwise not appropriate for our community, you are generally safe to delete it. + Our moderation bot is configured to log deleted messages automatically in the `#mod-actions` channel. If a message is not in line with our Code of Conduct, or otherwise not appropriate for our community, you are generally safe to delete it. Note that if the message contains content that violates Discord's terms of service, you'll want to report it via https://dis.gd/report **prior to** deleting it. diff --git a/docs/i18n/german/reply-templates.md b/docs/i18n/german/reply-templates.md index d5c5110346b..c9632e049b6 100644 --- a/docs/i18n/german/reply-templates.md +++ b/docs/i18n/german/reply-templates.md @@ -107,7 +107,7 @@ If you have any questions, feel free to ask questions on the ["Contributors" cat > When PR is invalid. ```markdown -Hey @username +Hey there, Thank you for opening this pull request. @@ -157,7 +157,7 @@ Thank you for your enthusiasm in contributing to our project. We eagerly await m **Happy Contributing!** 🌟 ``` -## Issue Not Triaged +## PR Opened While Issue Is Not Triaged > When a PR is opened for an issue that hasn't been triaged and marked as ready for contribution. @@ -234,3 +234,15 @@ Issues labeled with `help wanted` or `first timers only` are open for contributi Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you. ``` + +## Requests for Assignment While Issue Is Not Triaged + +> When a contributor requests for assignment but the issue hasn't been triaged or marked as ready for contribution. + +```md +Hi there, + +Thanks for your interest in contributing. + +This issue has not been triaged yet, and a solution has not been agreed upon. Once the issue is open for contribution, you are welcome to create a pull request to reflect the issue consensus. Please also note that we typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. +``` \ No newline at end of file diff --git a/docs/i18n/italian/how-to-open-a-pull-request.md b/docs/i18n/italian/how-to-open-a-pull-request.md index c0bf4141c5a..06d043c7474 100644 --- a/docs/i18n/italian/how-to-open-a-pull-request.md +++ b/docs/i18n/italian/how-to-open-a-pull-request.md @@ -7,19 +7,20 @@ Ci aspettiamo che i nostri contributori siano consapevoli del processo specifico Alcuni esempi di ciò sono: 1. Non modificare i file direttamente attraverso GitHub – nonostante sia possibile, non è una buona idea. -2. Assicurati di seguire la checklist della PR e non solo spuntare le cose; altrimenti, non ti prenderemo sul serio. -3. Usa il modo corretto per linkare le issue nella descrizione della PR aggiornando `XXXXXX`. Non basta aggiungere numeri di issue dappertutto o ovunque ti pare. -4. Non "@menzionare" o richiedere qualcuno per la revisione troppe volte. +2. Make sure the PR title follows [our convention](#prepare-a-good-pr-title). +3. Assicurati di seguire la checklist della PR e non solo spuntare le cose; altrimenti, non ti prenderemo sul serio. +4. Usa il modo corretto per linkare le issue nella descrizione della PR aggiornando `XXXXXX`. Non basta aggiungere numeri di issue dappertutto o ovunque ti pare. +5. Non "@menzionare" o richiedere qualcuno per la revisione troppe volte. Sappiamo che sei entusiasta di contribuire. Per quanto a un manutentore faccia piacere risponderti, si tratta di una persona impegnata che si occupa di centinaia di richieste proprio come la tua. Sii paziente, qualcuno ti risponderà prima o poi. -5. Non lavorare direttamente sul ramo (branch) `main` - crea un nuovo ramo per le modifiche su cui stai lavorando. +6. Non lavorare direttamente sul ramo (branch) `main` - crea un nuovo ramo per le modifiche su cui stai lavorando. > [!NOTE] La tua PR dovrebbe essere rivolta a modifiche del solo curriculum inglese. Per contribuire alle traduzioni invece, leggi [questa guida](index.md#traduzioni). ## Prepare a Good PR Title -Si consiglia di utilizzare [Titolo e messaggi convenzionali](https://www.conventionalcommits.org/) per i commit e le pull request. La convenzione ha il seguente formato: +We use [conventional title and messages](https://www.conventionalcommits.org/) for commits and pull requests. La convenzione ha il seguente formato: > `([ambito/i opzionale/i]): ` > @@ -27,7 +28,7 @@ Si consiglia di utilizzare [Titolo e messaggi convenzionali](https://www.convent > > `fix(learn): tests for the do...while loop challenge` -Ogni volta in cui apri una Pull Request (PR), puoi usare la seguente lista per determinare il tipo (type), l'ambito (scope) (opzionale) e la descrizione. +Whenever you open a Pull Request (PR), you can use the below to determine the type, scope (optional), and description. **Tipo:** @@ -81,7 +82,7 @@ Alcuni esempi di buoni titoli di PR sono: - Ti sarà presentato un modello di pull request. Questa è una lista di controllo che avresti dovuto seguire prima di aprire la pull request. - - Compila i dettagli come ritieni opportuno. Queste informazioni saranno esaminate e i revisori decideranno se la tua pull request è accettata. + - Compila i dettagli come ritieni opportuno. Ensure that you give the reviewers enough context to review the changes. If the PR makes changes to the UI, be sure to include screenshots of the changes as well. All of this information will be reviewed and the reviewers will decide whether or not your pull request is accepted. - Se la PR ha lo scopo di affrontare un'issue GitHub esistente, alla fine del corpo della descrizione della tua PR, usa la parola chiave _Closes_ con il numero dell'issue per [chiudere automaticamente questa issue se la PR è accettata](https://help.github.com/en/articles/closing-issues-using-keywords). @@ -91,7 +92,7 @@ Alcuni esempi di buoni titoli di PR sono: - Questo è molto importante quando si fanno cambiamenti che non sono solo modifiche a contenuto testuale come documentazione o descrizioni di sfide. Examples of changes that need local testing include JavaScript, CSS, or HTML, which could change the functionality or layout of a page. - - If your PR affects the behaviour of a page, it should be accompanied by corresponding [Cypress integration tests](how-to-add-cypress-tests.md). + - If your PR affects the behavior of a page, it should be accompanied by corresponding [Playwright integration tests](how-to-add-playwright-tests.md). ## Feedback on Pull Requests diff --git a/docs/i18n/italian/moderator-handbook.md b/docs/i18n/italian/moderator-handbook.md index 743f2ed4b09..dd22afb3578 100644 --- a/docs/i18n/italian/moderator-handbook.md +++ b/docs/i18n/italian/moderator-handbook.md @@ -201,7 +201,7 @@ If a user creates a thread asking for feedback on a solution, move the thread to ### Utenti Minorenni -Our [Terms of Service](https://freecodecamp.org/terms) require that freeCodeCamp users be at least 13 years of age. If a user reveals that they are under the age of 13, send them the message (below), suspend the account then **Email `support[at]freecodecamp.org` to delete the user's freeCodeCamp /learn and forum accounts as well (providing a link to the offending forum account).** +Our [Terms of Service](https://freecodecamp.org/terms) require that freeCodeCamp users be at least 13 years of age. If a user reveals that they are under the age of 13, send them the message below, suspend their account, then email the link of their forum account to `support[at]freecodecamp.org` for their freeCodeCamp /learn and forum accounts removal. ```markdown OGGETTO: Gli utenti al di sotto dei 13 anni di età non possono utilizzare il forum per i nostri Termini di Servizio. @@ -243,7 +243,7 @@ Here's how moderators deal with violations of our [Code of Conduct](https://code Per violazioni minori, può essere emesso un avviso con il comando `/warn`. Per violazioni più importanti, puoi rimuovere un membro dal server temporaneamente con il comando `/kick`, o permanentemente con il comando `/ban`. In alcuni casi, un membro potrebbe aver solo bisogno di tempo per calmarsi e riflettere - il comando `/mute` ti permette di impedirgli di dialogare con la community per un determinato periodo. Un membro su cui è stato usato il comando mute può vedere le conversazioni, ma non può pubblicare messaggi o aggiungere reazioni. - Tutti i comandi di moderazione richiederanno un parametro `reason`, che dovrebbe essere una breve spiegazione del perché l'azione è stata intrapresa. Le azioni di moderazione effettuate con il bot saranno registrate in `#mod-log`, che ci permette di rimanere tutti nella stessa pagina. Dovremmo evitare di utilizzare gli strumenti di moderazione integrati di Discord, in quanto non saranno registrati. + Tutti i comandi di moderazione richiederanno un parametro `reason`, che dovrebbe essere una breve spiegazione del perché l'azione è stata intrapresa. Moderation actions done with the bot will be logged in `#mod-actions`, which allows us all to stay on the same page. Dovremmo evitare di utilizzare gli strumenti di moderazione integrati di Discord, in quanto non saranno registrati. > [!WARNING] La ragione fornita al comando di moderazione sarà anche inclusa nel messaggio di notifica all'utente. Per favore, ricorda di essere professionale. @@ -257,7 +257,7 @@ Here's how moderators deal with violations of our [Code of Conduct](https://code 4. **Cancellare i messaggi** - Il nostro bot di moderazione è configurato per registrare automaticamente i messaggi eliminati nel canale `#mod-log`. Se un messaggio non è in linea con il nostro Codice di Condotta o non appropriato per la nostra comunità, in genere puoi eliminarlo con certezza. + Our moderation bot is configured to log deleted messages automatically in the `#mod-actions` channel. Se un messaggio non è in linea con il nostro Codice di Condotta o non appropriato per la nostra comunità, in genere puoi eliminarlo con certezza. Nota che se il messaggio contiene contenuti che violano i termini di servizio di Discord, dovrai segnalarlo tramite https://dis.gd/report **prima** di eliminarlo. diff --git a/docs/i18n/italian/reply-templates.md b/docs/i18n/italian/reply-templates.md index d5c5110346b..c9632e049b6 100644 --- a/docs/i18n/italian/reply-templates.md +++ b/docs/i18n/italian/reply-templates.md @@ -107,7 +107,7 @@ If you have any questions, feel free to ask questions on the ["Contributors" cat > When PR is invalid. ```markdown -Hey @username +Hey there, Thank you for opening this pull request. @@ -157,7 +157,7 @@ Thank you for your enthusiasm in contributing to our project. We eagerly await m **Happy Contributing!** 🌟 ``` -## Issue Not Triaged +## PR Opened While Issue Is Not Triaged > When a PR is opened for an issue that hasn't been triaged and marked as ready for contribution. @@ -234,3 +234,15 @@ Issues labeled with `help wanted` or `first timers only` are open for contributi Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you. ``` + +## Requests for Assignment While Issue Is Not Triaged + +> When a contributor requests for assignment but the issue hasn't been triaged or marked as ready for contribution. + +```md +Hi there, + +Thanks for your interest in contributing. + +This issue has not been triaged yet, and a solution has not been agreed upon. Once the issue is open for contribution, you are welcome to create a pull request to reflect the issue consensus. Please also note that we typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. +``` \ No newline at end of file diff --git a/docs/i18n/japanese/how-to-open-a-pull-request.md b/docs/i18n/japanese/how-to-open-a-pull-request.md index 754ee4ccf9b..2b772a5b731 100644 --- a/docs/i18n/japanese/how-to-open-a-pull-request.md +++ b/docs/i18n/japanese/how-to-open-a-pull-request.md @@ -7,19 +7,20 @@ We expect our contributors to be aware of the process specific to this project. Some examples of this are: 1. Do not edit files directly through GitHub – while you can, it's not a good idea. -2. Make sure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. -3. Use the correct way to link issues in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like. -4. Do not "@mention" or request someone for reviews too many times. +2. Make sure the PR title follows [our convention](#prepare-a-good-pr-title). +3. Make sure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. +4. Use the correct way to link issues in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like. +5. Do not "@mention" or request someone for reviews too many times. We understand you are excited about contributing. As much as a maintainer will love to get back to you, they are busy people looking after hundreds of requests just like yours. Be patient, someone will get to you sooner or later. -5. Do not work directly off your `main` branch - create a new branch for the changes you are working on. +6. Do not work directly off your `main` branch - create a new branch for the changes you are working on. > [!NOTE] Your PR should be targeting changes to the English curriculum only. Read [this guide](index.md#translations) instead for contributing to translations. ## Prepare a Good PR Title -We recommend using [conventional title and messages](https://www.conventionalcommits.org/) for commits and pull request. The convention has the following format: +We use [conventional title and messages](https://www.conventionalcommits.org/) for commits and pull requests. The convention has the following format: > `([optional scope(s)]): ` > @@ -27,7 +28,7 @@ We recommend using [conventional title and messages](https://www.conventionalcom > > `fix(learn): tests for the do...while loop challenge` -Whenever you open a Pull Request(PR), you can use the below to determine the type, scope (optional), and description. +Whenever you open a Pull Request (PR), you can use the below to determine the type, scope (optional), and description. **Type:** @@ -81,7 +82,7 @@ Some examples of good PR titles would be: - プルリクエストテンプレートが表示されます。 これはプルリクエストを開く前に行うべきチェックリストです。 - - 必要に応じて詳細を記入します。 この情報はレビューされ、レビュアーがプルリクエストを受け入れるかどうかを決定します。 + - 必要に応じて詳細を記入します。 Ensure that you give the reviewers enough context to review the changes. If the PR makes changes to the UI, be sure to include screenshots of the changes as well. All of this information will be reviewed and the reviewers will decide whether or not your pull request is accepted. - PR が既存の GitHub Issue に対処するものである場合、PR 説明本文の最後に、キーワード _Closes_ と Issue 番号を使用して、[ PR が承認されマージされたら、その Issue が自動的にクローズされるようにします](https://help.github.com/en/articles/closing-issues-using-keywords)。 @@ -91,7 +92,7 @@ Some examples of good PR titles would be: - これは、ドキュメントやチャレンジの説明のようなテキストコンテンツを編集するだけでなく、変更を加える場合に、非常に重要です。 Examples of changes that need local testing include JavaScript, CSS, or HTML, which could change the functionality or layout of a page. - - If your PR affects the behaviour of a page, it should be accompanied by corresponding [Cypress integration tests](how-to-add-cypress-tests.md). + - If your PR affects the behavior of a page, it should be accompanied by corresponding [Playwright integration tests](how-to-add-playwright-tests.md). ## Feedback on Pull Requests diff --git a/docs/i18n/japanese/moderator-handbook.md b/docs/i18n/japanese/moderator-handbook.md index 032be8c3dd3..9a1980589fc 100644 --- a/docs/i18n/japanese/moderator-handbook.md +++ b/docs/i18n/japanese/moderator-handbook.md @@ -201,7 +201,7 @@ If a user creates a thread asking for feedback on a solution, move the thread to ### Underage Users -Our [Terms of Service](https://freecodecamp.org/terms) require that freeCodeCamp users be at least 13 years of age. If a user reveals that they are under the age of 13, send them the message (below), suspend the account then **Email `support[at]freecodecamp.org` to delete the user's freeCodeCamp /learn and forum accounts as well (providing a link to the offending forum account).** +Our [Terms of Service](https://freecodecamp.org/terms) require that freeCodeCamp users be at least 13 years of age. If a user reveals that they are under the age of 13, send them the message below, suspend their account, then email the link of their forum account to `support[at]freecodecamp.org` for their freeCodeCamp /learn and forum accounts removal. ```markdown SUBJECT: Users under 13 are not allowed to use the forum per our Terms of Service. @@ -243,7 +243,7 @@ Here's how moderators deal with violations of our [Code of Conduct](https://code For minor offences, a warning may be issued with the `/warn` command. For more egregious offences, you can remove the member from the server temporarily with the `/kick` command, or permanently with the `/ban` command. In some cases, a member may just need some time to cool off and collect their thoughts - the `/mute` command allows you to prevent them from engaging with our community for a set period of time. A muted member can see the conversation, but cannot post messages or add reactions. - All moderation commands will take a `reason` parameter, which should be a short explanation of why the action was taken. Moderation actions done with the bot will be logged in `#mod-log`, which allows us all to stay on the same page. As such, we should avoid using Discord's built-in moderation tools, as they will not be logged. + All moderation commands will take a `reason` parameter, which should be a short explanation of why the action was taken. Moderation actions done with the bot will be logged in `#mod-actions`, which allows us all to stay on the same page. As such, we should avoid using Discord's built-in moderation tools, as they will not be logged. > [!WARNING] The reason provided to a moderation command will also be included in the DM notification to the camper. Please remember to be professional here. @@ -257,7 +257,7 @@ Here's how moderators deal with violations of our [Code of Conduct](https://code 4. **Deleting messages** - Our moderation bot is configured to log deleted messages automatically in the `#mod-log` channel. If a message is not in line with our Code of Conduct, or otherwise not appropriate for our community, you are generally safe to delete it. + Our moderation bot is configured to log deleted messages automatically in the `#mod-actions` channel. If a message is not in line with our Code of Conduct, or otherwise not appropriate for our community, you are generally safe to delete it. Note that if the message contains content that violates Discord's terms of service, you'll want to report it via https://dis.gd/report **prior to** deleting it. diff --git a/docs/i18n/japanese/reply-templates.md b/docs/i18n/japanese/reply-templates.md index d5c5110346b..c9632e049b6 100644 --- a/docs/i18n/japanese/reply-templates.md +++ b/docs/i18n/japanese/reply-templates.md @@ -107,7 +107,7 @@ If you have any questions, feel free to ask questions on the ["Contributors" cat > When PR is invalid. ```markdown -Hey @username +Hey there, Thank you for opening this pull request. @@ -157,7 +157,7 @@ Thank you for your enthusiasm in contributing to our project. We eagerly await m **Happy Contributing!** 🌟 ``` -## Issue Not Triaged +## PR Opened While Issue Is Not Triaged > When a PR is opened for an issue that hasn't been triaged and marked as ready for contribution. @@ -234,3 +234,15 @@ Issues labeled with `help wanted` or `first timers only` are open for contributi Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you. ``` + +## Requests for Assignment While Issue Is Not Triaged + +> When a contributor requests for assignment but the issue hasn't been triaged or marked as ready for contribution. + +```md +Hi there, + +Thanks for your interest in contributing. + +This issue has not been triaged yet, and a solution has not been agreed upon. Once the issue is open for contribution, you are welcome to create a pull request to reflect the issue consensus. Please also note that we typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. +``` \ No newline at end of file diff --git a/docs/i18n/portuguese/how-to-open-a-pull-request.md b/docs/i18n/portuguese/how-to-open-a-pull-request.md index b9ef1984b01..31f27157045 100644 --- a/docs/i18n/portuguese/how-to-open-a-pull-request.md +++ b/docs/i18n/portuguese/how-to-open-a-pull-request.md @@ -7,19 +7,20 @@ Esperamos que nossos colaboradores estejam cientes do processo específico deste Alguns exemplos disso são: 1. Não edite arquivos diretamente no GitHub – enquanto você puder, não é uma boa ideia. -2. Certifique-se de seguir a lista de verificação de PR e não apenas desmarcar as coisas; caso contrário, não levaremos você a sério. -3. Utilize a maneira correta de ligar issues na descrição do PR, atualizando o `XXXXXX`. Não adicione apenas números de issues em todo e qualquer lugar e que quiser. -4. Não faça menções com @ nem solicite as revisões de outra pessoa diversas vezes. +2. Make sure the PR title follows [our convention](#prepare-a-good-pr-title). +3. Certifique-se de seguir a lista de verificação de PR e não apenas desmarcar as coisas; caso contrário, não levaremos você a sério. +4. Utilize a maneira correta de ligar issues na descrição do PR, atualizando o `XXXXXX`. Não adicione apenas números de issues em todo e qualquer lugar e que quiser. +5. Não faça menções com @ nem solicite as revisões de outra pessoa diversas vezes. Entendemos que você está animado para contribuir. Por mais que os mantenedores adorem a ideia de responder você, lembre-se de que eles são pessoas ocupadas que cuidam de centenas de solicitações como as suas. Seja paciente, alguém responderá você mais cedo ou mais tarde. -5. Não trabalhe diretamente na branch `main` - crie uma outra branch para as alterações em que está trabalhando. +6. Não trabalhe diretamente na branch `main` - crie uma outra branch para as alterações em que está trabalhando. > [!NOTE] Seu PR deve se destinar apenas a alterações no currículo em inglês. Veja [este guia](index.md#translations) para contribuir com traduções. ## Prepare um bom título para o PR -Recomendamos usar [título e mensagens convencionais](https://www.conventionalcommits.org/) para commits e pull request. A convenção tem o seguinte formato: +We use [conventional title and messages](https://www.conventionalcommits.org/) for commits and pull requests. A convenção tem o seguinte formato: > `([escopo(s) opcional(is)]): ` > @@ -27,7 +28,7 @@ Recomendamos usar [título e mensagens convencionais](https://www.conventionalco > > `fix(learn): testes para o desafio de ciclo do...while` -Sempre que abrir um Pull Request (PR), você pode usar a referência abaixo para determinar o tipo, escopo (opcional) e a descrição. +Whenever you open a Pull Request (PR), you can use the below to determine the type, scope (optional), and description. **Tipo:** @@ -81,7 +82,7 @@ Alguns exemplos de bons títulos de PRs seriam: - Será apresentado um modelo de pull request. É uma checklist que você deve seguir antes de abrir o pull request. - - Preencha os detalhes como quiser. Essas informações serão revisadas e os revisores decidirão se seu pull request será aceito ou não. + - Preencha os detalhes como quiser. Ensure that you give the reviewers enough context to review the changes. If the PR makes changes to the UI, be sure to include screenshots of the changes as well. All of this information will be reviewed and the reviewers will decide whether or not your pull request is accepted. - Se o PR tem como objetivo resolver uma issue GitHub existente, então, no final do corpo da descrição de seu PR, use a palavra-chave _Closes_ com o número da issue para [automaticamente fechá-la, se o PR for aceito e dado merge](https://help.github.com/en/articles/closing-issues-using-keywords). @@ -91,7 +92,7 @@ Alguns exemplos de bons títulos de PRs seriam: - Isso é muito importante quando se está fazendo mudanças que não são apenas edições no conteúdo do texto como a documentação ou descrição de um desafio. Exemplos de mudanças que precisam ser testadas localmente incluem JavaScript, CSS ou HTML que podem mudar a funcionalidade ou aparência de uma página. - - Se seu PR afeta o comportamento de uma página, ele deve estar acompanhado pelo correspondente [teste de integração Cypress](how-to-add-cypress-tests.md). + - If your PR affects the behavior of a page, it should be accompanied by corresponding [Playwright integration tests](how-to-add-playwright-tests.md). ## Comentários nos pull requests diff --git a/docs/i18n/portuguese/moderator-handbook.md b/docs/i18n/portuguese/moderator-handbook.md index 81f8cc6a4c9..188a79f107a 100644 --- a/docs/i18n/portuguese/moderator-handbook.md +++ b/docs/i18n/portuguese/moderator-handbook.md @@ -201,7 +201,7 @@ Se um usuário criar uma thread pedindo feedback de uma solução, mova o tópic ### Usuários menores de idade -Nossos [termos de serviço](https://freecodecamp.org/terms) requerem que os usuários do freeCodeCamp tenham, pelo menos, 13 anos de idade. Se um usuário revelar que ele tem menos de 13 anos de idade, envie-lhe a mensagem abaixo e suspenda a conta. Em seguida, **envie um email para `support[at]freecodecamp.org` para excluir as contas do usuário de freeCodeCamp/learn e do fórum (fornecendo um link para a conta ilícita do fórum).** +Nossos [termos de serviço](https://freecodecamp.org/terms) requerem que os usuários do freeCodeCamp tenham, pelo menos, 13 anos de idade. If a user reveals that they are under the age of 13, send them the message below, suspend their account, then email the link of their forum account to `support[at]freecodecamp.org` for their freeCodeCamp /learn and forum accounts removal. ```markdown ASSUNTO: Usuários com menos de 13 anos não têm permissão para usar o fórum de acordo com os nossos Termos de Serviço. @@ -243,7 +243,7 @@ Mas se é um delito flagrante, isso não pode razoavelmente ser atribuído a uma Para delitos menores, um aviso pode ser emitido com o comando `/warn`. Para mais erros flagrantes, você pode remover o membro do servidor temporariamente com o comando `/kick` ou permanentemente com o comando `/ban`. Em alguns casos, um membro pode precisar de algum tempo para resfriar e coletar seus pensamentos - o comando `/mute` permite que você evite que ele se envolva com a nossa comunidade por um determinado período de tempo. Um membro silenciado pode ver a conversa, mas não pode postar mensagens ou adicionar reações. - Todos os comandos de moderação levarão um parâmetro `reason`, que deve ser uma breve explicação do motivo da ação ter sido tomada. As ações de moderação feitas com o bot serão registradas em `#mod-log`, o que nos permite a todos ficar na mesma página. Como tal, devemos evitar o uso das ferramentas de moderação embutidas no Discord, pois elas não serão registradas. + Todos os comandos de moderação levarão um parâmetro `reason`, que deve ser uma breve explicação do motivo da ação ter sido tomada. Moderation actions done with the bot will be logged in `#mod-actions`, which allows us all to stay on the same page. Como tal, devemos evitar o uso das ferramentas de moderação embutidas no Discord, pois elas não serão registradas. > [!WARNING] A razão fornecida para um comando de moderação também será incluída na notificação de DM ao camper. Por favor, lembre-se de ser profissional aqui. @@ -257,7 +257,7 @@ Mas se é um delito flagrante, isso não pode razoavelmente ser atribuído a uma 4. **Apagando mensagens** - Nosso bot de moderação está configurado para registrar automaticamente mensagens excluídas no canal `#mod-log`. Se uma mensagem não estiver de acordo com o nosso Código de Conduta, ou não é apropriado para a nossa comunidade, geralmente você pode excluí-la. + Our moderation bot is configured to log deleted messages automatically in the `#mod-actions` channel. Se uma mensagem não estiver de acordo com o nosso Código de Conduta, ou não é apropriado para a nossa comunidade, geralmente você pode excluí-la. Note que se a mensagem contiver conteúdo que viole os termos de serviço do Discord, você deverá denunciá-la em https://dis.gd/report **antes de** excluí-la. diff --git a/docs/i18n/portuguese/reply-templates.md b/docs/i18n/portuguese/reply-templates.md index de90619e4e9..48b291de47e 100644 --- a/docs/i18n/portuguese/reply-templates.md +++ b/docs/i18n/portuguese/reply-templates.md @@ -107,7 +107,7 @@ If you have any questions, feel free to ask questions on the ["Contributors" cat > Quando um PR é inválido. ```markdown -Hey @username +Hey there, Thank you for opening this pull request. @@ -157,7 +157,7 @@ Thank you for your enthusiasm in contributing to our project. We eagerly await m **Happy Contributing!** 🌟 ``` -## Issue não passou por triagem +## PR Opened While Issue Is Not Triaged > Quando um PR é aberto para uma issue que não passou por triagem e marcada como pronta para contribuição. @@ -234,3 +234,15 @@ Issues labeled with `help wanted` or `first timers only` are open for contributi Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you. ``` + +## Requests for Assignment While Issue Is Not Triaged + +> When a contributor requests for assignment but the issue hasn't been triaged or marked as ready for contribution. + +```md +Hi there, + +Thanks for your interest in contributing. + +This issue has not been triaged yet, and a solution has not been agreed upon. Once the issue is open for contribution, you are welcome to create a pull request to reflect the issue consensus. Please also note that we typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. +``` \ No newline at end of file diff --git a/docs/i18n/ukrainian/how-to-open-a-pull-request.md b/docs/i18n/ukrainian/how-to-open-a-pull-request.md index 0c752e7b862..360c42cbb89 100644 --- a/docs/i18n/ukrainian/how-to-open-a-pull-request.md +++ b/docs/i18n/ukrainian/how-to-open-a-pull-request.md @@ -7,19 +7,20 @@ Деякі приклади: 1. Не редагуйте файли напряму через GitHub, це не дуже хороша ідея. -2. Переконайтесь, що дотримуєтесь контрольного списку PR, а не просто ставите галочки. В такому випадку ми не сприйматимемо вас серйозно. -3. Використовуйте правильний спосіб пов’язати завдання в описі PR, оновивши `XXXXXX`. Не додавайте номери завдань будь-де. -4. Не «@згадуйте» чи запитуйте відгук кілька разів. +2. Make sure the PR title follows [our convention](#prepare-a-good-pr-title). +3. Переконайтесь, що дотримуєтесь контрольного списку PR, а не просто ставите галочки. В такому випадку ми не сприйматимемо вас серйозно. +4. Використовуйте правильний спосіб пов’язати завдання в описі PR, оновивши `XXXXXX`. Не додавайте номери завдань будь-де. +5. Не «@згадуйте» чи запитуйте відгук кілька разів. Ми розуміємо, що ви раді зробити свій внесок. Модераторам подобається відповідати кожному, однак пам’ятайте: вони зайняті люди, які розглядають сотні запитів. Рано чи пізно, хтось дійде і до вашого запиту. -5. Не працюйте напряму зі своєї гілки `main`. Створіть нову гілку для змін, над якими ви працюєте. +6. Не працюйте напряму зі своєї гілки `main`. Створіть нову гілку для змін, над якими ви працюєте. > [!NOTE] Ваш PR повинен націлюватись лише на зміни навчальної програми англійською мовою. Див. [цей довідник](index.md#translations), щоб зробити внесок до перекладу. ## Підготуйте хороший заголовок для PR -Ми рекомендуємо використовувати [ загальноприйняті заголовки та повідомлення](https://www.conventionalcommits.org/) для комітів і запитів на злиття. Конвенція вимагає наступного формату: +We use [conventional title and messages](https://www.conventionalcommits.org/) for commits and pull requests. Конвенція вимагає наступного формату: > `<тип>([область (необов’язково)]): <опис>` > @@ -27,7 +28,7 @@ > > `fix(learn): тести для завдання з циклу do...while` -Щоразу, коли ви відкриваєте запит на злиття (PR), використовуйте нижчеподану інформацію, щоб визначити тип, область та опис. +Whenever you open a Pull Request (PR), you can use the below to determine the type, scope (optional), and description. **Тип:** @@ -81,7 +82,7 @@ - Вам буде надано шаблон PR. Це список, якого потрібно дотримуватись перед відкриттям PR. - - Заповніть деталі, які ви вважаєте за потрібне. Ця інформація буде розглянута, а модератори вирішать, чи ваш PR буде прийнятий. + - Заповніть деталі, які ви вважаєте за потрібне. Ensure that you give the reviewers enough context to review the changes. If the PR makes changes to the UI, be sure to include screenshots of the changes as well. All of this information will be reviewed and the reviewers will decide whether or not your pull request is accepted. - Якщо PR призначений для вирішення наявного завдання на GitHub, то використайте ключове слово _Closes_ та номер завдання в кінці опису, щоб [автоматично закрити цю проблему, якщо PR прийнятий та об’єднаний](https://help.github.com/en/articles/closing-issues-using-keywords). @@ -91,7 +92,7 @@ - Це надзвичайно важливо при внесенні змін, які не стосуються зміни тексту (наприклад, документації чи опису завдань). До змін, яким потрібне локальне тестування, входять JavaScript, CSS або HTML (тобто ті, які можуть змінити функціональність чи макет сторінки). - - Якщо ваш PR впливає на поведінку сторінки, він повинен супроводжуватися [інтеграційними тестами Cypress](how-to-add-cypress-tests.md). + - If your PR affects the behavior of a page, it should be accompanied by corresponding [Playwright integration tests](how-to-add-playwright-tests.md). ## Зворотний зв’язок по PR diff --git a/docs/i18n/ukrainian/how-to-work-on-coding-challenges.md b/docs/i18n/ukrainian/how-to-work-on-coding-challenges.md index 48fd864b349..6d4bf392fef 100644 --- a/docs/i18n/ukrainian/how-to-work-on-coding-challenges.md +++ b/docs/i18n/ukrainian/how-to-work-on-coding-challenges.md @@ -203,95 +203,95 @@ console.log('freeCodeCamp is awesome!'); # --scene-- ```json -// # --scene-- can only consist of a single json object +// # --scene-- може складатись лише з одного об’єкту json { - // Setup the scene. Properties not marked optional are required. + // Налаштуйте дію. Властивості, не позначені як додаткові, є обов’язковими. "setup": { - // Background file to start the scene. A list of scene asset filenames can be found here: https://github.com/freeCodeCamp/cdn/pull/233/files + // Файл фону, щоб запустити дію. Список всіх файлів можна знайти тут: https://github.com/freeCodeCamp/cdn/pull/233/files "background": "company2-center.png", - // Array of all characters that will appear in the scene + // Масив всіх персонажів, які з’являться на місці дії "characters": [ { - // Name of character. See list of available characters in scene-assets.tsx + // Ім’я персонажа. Список доступних персонажів знаходиться в scene-assets.tsx "character": "Maria", - // Where to start the character. Maria will start off screen to the left + // Де з’являється персонаж. Марія з’явиться на екрані ліворуч "position": { "x": -25, "y": 0, "z": 1 } }, { "character": "Tom", - // Tom will start 70% from the left of the screen and 1.5 times regular size + // Том з’явиться на 70% ліворуч та буде в 1,5 рази більший за звичайний розмір. "position": { "x": 70, "y": 0, "z": 1.5 }, - // Optional, defaults to 1. Tom will start invisible + // Необов’язково, за замовчуванням 1. Спочатку Том буде невидимим "opacity": 0 } ], "audio": { // Audio filename "filename": "1.1-1.mp3", - // Seconds after the scene starts before the audio starts playing + // Секунди після початку дії до початку програвання аудіо "startTime": 1.3, - // Optional. Timestamp of the audio file where it starts playing from. + // Необов’язково. Часова мітка аудіофайлу, з якого він починає відтворюватися. "startTimestamp": 0, - // Optional. Timestamp of the audio file where is stops playing. If these two aren't used, the whole audio file will play. + // Необов’язково. Часова мітка аудіофайлу, з якого він перестає відтворюватися. Якщо ці мітки не використати, аудіофайл відтвориться повністю. "finishTimestamp": 8.4 }, - // Optional, defaults to false. Use this for the long dialogues. It stops the accessibility icon from showing which gives campers the option to show or hide the dialogue text + // Необов’язково, за замовчуванням false. Використовуйте для довгих діалогів. Це призводить до того, що іконка доступності не відображається, що дає користувачам змогу показувати або приховувати текст діалогу "alwaysShowDialogue": true }, - // Array of commands that make up the scene + // Масив команд, з яких складається дія "commands": [ { - // Character that will have an action for this command + // Персонаж, який виконує цю команду "character": "Maria", - // Optional, defaults to previous value. Maria will move to 25% from the left of the screen. The movement takes 0.5 seconds + // Необов’язково, за замовчуванням попереднє значення. Марія переміститься на 25% ліворуч від екрана. Переміщення триває 0,5 секунди "position": { "x": 25, "y": 0, "z": 1 }, - // When the command will start. Zero seconds after the camper presses play + // Коли розпочнеться команда. Нуль секунд після того, як користувач натисне програвання "startTime": 0 }, { "character": "Tom", - // Optional, defaults to previous value. Tom will fade into view. The transition take 0.5 seconds. Movement and Opacity transitions take 0.5 seconds + // Необов’язково, за замовчуванням попереднє значення. Том з’явиться, розчиняючись. Перехід триває 0,5 секунди. Переміщення та непрозорість займають 0,5 секунди "opacity": 1, - // Tom will fade into view 0.5 seconds into the scene (immediately after Maria finishes moving on screen) + // Том з’явиться на екрані через 0,5 секунди (одразу після того, як Марія завершить переміщення) "startTime": 0.5 }, { "character": "Maria", - // When the command starts: Maria will start saying this line 1.3 seconds into the scene. Note that this is the same time as the audio.startTime above. It doesn't have to match that (maybe there's a pause at the begninning of the audio or something) + // Коли розпочнеться команда, Марія почне вимовляти цей рядок через 1,3 секунди після початку. Зверніть увагу, що час той самий, що й для audio.startTime вище. Вони необов’язково збігатимуться (можливо, на початку аудіо є пауза чи щось інше) "startTime": 1.3, - // The character will stop moving their mouth at the finishTime + // Персонаж перестане рухати ротом на finishTime "finishTime": 4.95, "dialogue": { - // Text that will appear if the dialogue is visible + // Текст, який з’явиться, якщо діалог видимий "text": "Hello! You're the new graphic designer, right? I'm Maria, the team lead.", - // Where the dialogue text will be aligned. Can be 'left', 'center', or 'right' + // Вирівнювання тексту діалогу. Може бути 'left', 'center' або 'right' "align": "left" } }, { - // background will change to this at 5.4 seconds into the scene + // фон зміниться на інший через 5,4 секунд від початку дії "background": "company2-breakroom.png", "character": "Tom", "startTime": 5.4, "finishTime": 9.4, "dialogue": { "text": "Hi, that's right! I'm Tom McKenzie. It's a pleasure to meet you.", - // Tom's text will be aligned to the right since he is on the right side of the screen + // Текст Тома буде вирівняний за правим краєм, оскільки він розташований праворуч "align": "right" } }, { "character": "Tom", - // Tom will fade to 0 opacity + // Том розчиниться "opacity": 0, - // I like to move characters off screen or fade them 0.5 second after the last talking command + // За бажанням можна переміщувати персонажів за межі екрану або розчинити їх через 0,5 секунди після останнього говоріння "startTime": 9.9 }, { "character": "Maria", - // Maria will slide back off the screen to the left + // Марія переміститься ліворуч "position": { "x": -25, "y": 0, "z": 1 }, - // The animation will stop playing 0.5 seconds after the 'finishTime' of the last command - or 0.5 seconds after 'startTime' if 'finishTime' isn't there. + // Анімація припинить відтворення через 0,5 секунди після 'finishTime' останньої команди, або через 0,5 секунди після 'startTime', якщо 'finishTime' немає. "startTime": 10.4 } ] diff --git a/docs/i18n/ukrainian/how-to-work-on-localized-client-webapp.md b/docs/i18n/ukrainian/how-to-work-on-localized-client-webapp.md index 7e798c9863c..bf2050cd834 100644 --- a/docs/i18n/ukrainian/how-to-work-on-localized-client-webapp.md +++ b/docs/i18n/ukrainian/how-to-work-on-localized-client-webapp.md @@ -254,7 +254,7 @@ const email = 'team@freecodecamp.org'; Щоб змінити текст клієнтської частини, перейдіть до відповідного файлу `.json`, знайдіть ключ, який використовується у компоненті React, та змініть його значення на новий текст. Шукайте цей ключ у кодовій базі, щоб переконатися, що він не використовується в іншому місці. Якщо використовується, переконайтесь, чи є сенс застосовувати зміни. -Run `pnpm run clean-and-develop` to apply the change. +Запустіть `pnpm run clean-and-develop`, щоб застосувати зміни. ## Додавання тексту @@ -264,11 +264,11 @@ Run `pnpm run clean-and-develop` to apply the change. > [!NOTE] Використовуйте англомовний текст для усіх мов, якщо файл перекладається на Crowdin. Якщо ви цього не зробите, тести не пройдуть. -Також було б добре тримати усі ключі в одному порядку для усіх файлів. Also, try to put all punctuation, spacing, quotes, etc. in the JSON files and not in the components or server files. +Також було б добре тримати усі ключі в одному порядку для усіх файлів. Спробуйте розставити всю пунктуацію, інтервали, лапки тощо у файлах JSON, а не у файлах компонента чи сервера. > [!NOTE] Підкреслення (`_`) є зарезервованим знаком для ключів у файлах клієнтської частини. Див. [документацію](https://www.i18next.com/translation-function/plurals) про те, як вони використовуються. -Run `pnpm run clean-and-develop` to apply the change. +Запустіть `pnpm run clean-and-develop`, щоб застосувати зміни. ## Запропонуйте запит на злиття (PR) diff --git a/docs/i18n/ukrainian/moderator-handbook.md b/docs/i18n/ukrainian/moderator-handbook.md index 23e4f5d8485..2ae2c6ee759 100644 --- a/docs/i18n/ukrainian/moderator-handbook.md +++ b/docs/i18n/ukrainian/moderator-handbook.md @@ -201,7 +201,7 @@ ### Користувачі, які не досягнули відповідного віку -Наші [Умови користування](https://freecodecamp.org/terms) вимагають, щоб користувачі freeCodeCamp досягли 13-річного віку. Якщо користувач зізнався, що не досягнув 13-річного віку, надішліть йому повідомлення (нижче) та призупиніть обліковий запис. Потім **напишіть на `support[at]freecodecamp.org` для видалення облікових записів на /learn та форумі (із посиланням на обліковий запис на форумі).** +Наші [Умови користування](https://freecodecamp.org/terms) вимагають, щоб користувачі freeCodeCamp досягли 13-річного віку. If a user reveals that they are under the age of 13, send them the message below, suspend their account, then email the link of their forum account to `support[at]freecodecamp.org` for their freeCodeCamp /learn and forum accounts removal. ```markdown SUBJECT: Users under 13 are not allowed to use the forum per our Terms of Service. @@ -243,7 +243,7 @@ Thank you for understanding. Через незначне порушення можна видати попередження за допомогою команди `/warn`. Через грубші порушення користувача можна видалити із сервера тимчасово (за допомогою команди `/kick`) або назавжди (за допомогою команди `/ban`). У деяких випадках користувачу просто потрібен час, щоб охолонути та зібрати свої думки: команда `/mute` дозволяє запобігти взаємодії користувача зі спільнотою на встановлений час. Заглушений користувач бачить розмову, але не може публікувати повідомлення чи додавати реакції. - Усі модераційні команди приймають параметр `reason`, що вимагає короткого пояснення вжитих дій. Модераційні дії, виконані із допомогою бота, будуть записані до `#mod-log`, що дозволяє нам залишатись на одній хвилі. Вбудовані інструменти дискорду не записуються, тому їх потрібно уникати. + Усі модераційні команди приймають параметр `reason`, що вимагає короткого пояснення вжитих дій. Moderation actions done with the bot will be logged in `#mod-actions`, which allows us all to stay on the same page. Вбудовані інструменти дискорду не записуються, тому їх потрібно уникати. > [!WARNING] Причина модераційної команди буде додана до особистого повідомлення користувачу. Не забудьте бути професіоналом. @@ -257,7 +257,7 @@ Thank you for understanding. 4. **Видалення повідомлень** - Наш бот автоматично вносить видалені повідомлення до каналу `#mod-log`. Якщо повідомлення не відповідає нашому Кодексу поведінки або є неприпустимим для нашої спільноти, його можна видалити. + Our moderation bot is configured to log deleted messages automatically in the `#mod-actions` channel. Якщо повідомлення не відповідає нашому Кодексу поведінки або є неприпустимим для нашої спільноти, його можна видалити. Зауважте: якщо повідомлення порушує умови використання дискорду, про це потрібно повідомити через https://dis.gd/report **перед** видаленням. diff --git a/docs/i18n/ukrainian/reply-templates.md b/docs/i18n/ukrainian/reply-templates.md index 27fe7a8889b..9569ea2c8d0 100644 --- a/docs/i18n/ukrainian/reply-templates.md +++ b/docs/i18n/ukrainian/reply-templates.md @@ -107,7 +107,7 @@ If you have any questions, feel free to ask questions on the ["Contributors" cat > Якщо PR недійсний. ```markdown -Hey @username +Hey there, Thank you for opening this pull request. @@ -157,7 +157,7 @@ Thank you for your enthusiasm in contributing to our project. We eagerly await m **Happy Contributing!** 🌟 ``` -## Невідсортоване завдання +## PR Opened While Issue Is Not Triaged > Якщо PR відкрито для завдання, яке не відсортоване та не позначене як готове для внеску. @@ -234,3 +234,15 @@ Issues labeled with `help wanted` or `first timers only` are open for contributi Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you. ``` + +## Requests for Assignment While Issue Is Not Triaged + +> When a contributor requests for assignment but the issue hasn't been triaged or marked as ready for contribution. + +```md +Hi there, + +Thanks for your interest in contributing. + +This issue has not been triaged yet, and a solution has not been agreed upon. Once the issue is open for contribution, you are welcome to create a pull request to reflect the issue consensus. Please also note that we typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. +``` \ No newline at end of file diff --git a/docs/i18n/ukrainian/troubleshooting-development-issues.md b/docs/i18n/ukrainian/troubleshooting-development-issues.md index d0b66f927fa..607ac5b8193 100644 --- a/docs/i18n/ukrainian/troubleshooting-development-issues.md +++ b/docs/i18n/ukrainian/troubleshooting-development-issues.md @@ -14,7 +14,7 @@ ## Проблеми відсутніх UI, шрифтів, мовних рядків чи помилки збірки -When you build the client, Gatsby will cache the fonts, language strings, and UI. Якщо щось з переліченого не кешоване, виконайте наступне: +Коли ви будуєте клієнта, Gatsby кешує шрифти, мовні рядки та UI. Якщо щось з переліченого не кешоване, виконайте наступне: ```bash pnpm run clean