mirror of
https://github.com/freeCodeCamp/freeCodeCamp.git
synced 2026-01-05 12:06:36 -05:00
chore(i18n,docs): processed translations (#50111)
This commit is contained in:
camperbot
@@ -148,6 +148,40 @@ export default connect(null, mapDispatchToProps)(MyComponent);
|
||||
<!-- ### Redux Types File -->
|
||||
<!-- The types associated with the Redux store state are located in `client/src/redux/types.ts`... -->
|
||||
|
||||
## API
|
||||
|
||||
### Testing
|
||||
|
||||
The `api/` tests are split into two parts:
|
||||
|
||||
1. Unit tests
|
||||
2. Integration tests
|
||||
|
||||
#### Unit Tests
|
||||
|
||||
Unit tests isolate a single function or component. The tests do not need mocking, but will require fixtures.
|
||||
|
||||
The unit tests are located in a new file adjacent the file exporting that being tested:
|
||||
|
||||
```text
|
||||
api/
|
||||
├── src/
|
||||
│ ├── utils.ts
|
||||
│ ├── utils.test.ts
|
||||
```
|
||||
|
||||
#### Integration Tests
|
||||
|
||||
Integration tests test the API as a whole. The tests will require mocking, and should not require fixtures beyond the database seeding data, and a method to authenticate.
|
||||
|
||||
Typically, each integration test file will be directly related to a route. The integration tests are located in the `api/tests/` directory:
|
||||
|
||||
```text
|
||||
api/
|
||||
├── tests/
|
||||
│ ├── settings.ts
|
||||
```
|
||||
|
||||
## Further Literature
|
||||
|
||||
- [TypeScript Docs](https://www.typescriptlang.org/docs/)
|
||||
|
||||
@@ -305,16 +305,6 @@ If you are approved, we will add you to our moderator teams on [GitHub](https://
|
||||
>
|
||||
> This is required for us to be able to give you write access to some of our repositories.
|
||||
|
||||
## How We Retire Inactive Moderators
|
||||
|
||||
Please note that we will frequently remove moderators whom we think are inactive. When we do this, we will send the following message:
|
||||
|
||||
```markdown
|
||||
This is a standard message notifying you that, since you don't seem to have been an active moderator recently, we're removing you from our moderator team. We deeply appreciate your help in the past.
|
||||
|
||||
If you think we did this in error, or once you're ready to come back and contribute more, just reply to this message letting us know.
|
||||
```
|
||||
|
||||
## How Our Contributors Room Works
|
||||
|
||||
Anyone is welcome in the [contributors room on our chat server](https://discord.gg/PRyKn3Vbay). It is the designated chat room for moderators and other campers who contribute to our community in any number of ways, including through study groups.
|
||||
@@ -488,19 +478,38 @@ If you think we're wrong in closing this issue, please request for it to be reop
|
||||
### Adding Comment About Newbie Mistakes
|
||||
|
||||
```markdown
|
||||
As a new contributor, we encourage you to read our [contributing guidelines](https://contribute.freecodecamp.org).
|
||||
Hi there,
|
||||
|
||||
We expect our contributors to be aware of the process specific to this project. Following the guidelines religiously earns you the respect of fellow maintainers and saves everyone time.
|
||||
Thanks for creating this pull request.
|
||||
|
||||
Some examples of this are:
|
||||
Please ensure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. Respect the requirements to earn the respect of your fellow maintainers. You will also save everyone time :)
|
||||
|
||||
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. Keep mentions and review requests to a minimum. We understand you are excited about contributing, and our maintainers will get back to you as soon as they get a chance.
|
||||
5. Do not work directly off your `main` branch - create a new branch for the changes you are working on.
|
||||
Since you are new here, please slow down and read our [contributing guidelines](https://contribute.freecodecamp.org), as we see that you may still need to catch up on a few things.
|
||||
|
||||
We appreciate you taking the time to help us, and we hope to see more contributions from you.
|
||||
<details>
|
||||
<summary>Here are some examples (expand)</summary>
|
||||
|
||||
1. Do not edit files directly on GitHub – while you can, it's not a good idea.
|
||||
|
||||
Typos and formatting errors can break the tests.
|
||||
|
||||
2. Use the correct way to link issues.
|
||||
|
||||
Add the issue number only in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like.
|
||||
|
||||
4. Keep mentions and review requests to a minimum.
|
||||
|
||||
We understand you are excited about contributing, and our maintainers will get back to you when they can.
|
||||
|
||||
5. Do not work directly off your `main` branch.
|
||||
|
||||
You can always create a new branch for the changes you are working on. That way, you can sync change to your PR branch as the main repository moves ahead while your PR is waiting in the merge queue.
|
||||
|
||||
</details>
|
||||
|
||||
Don't worry. You don't have to close this PR. Feel free to ask specific queries on improving your PR here; someone will guide you.
|
||||
|
||||
We are happy you are excited to contribute and appreciate you taking the time to help us. Looking forward to more contributions!
|
||||
|
||||
Happy Contributing.
|
||||
```
|
||||
|
||||
@@ -148,6 +148,40 @@ export default connect(null, mapDispatchToProps)(MyComponent);
|
||||
<!-- ### Redux Types File -->
|
||||
<!-- The types associated with the Redux store state are located in `client/src/redux/types.ts`... -->
|
||||
|
||||
## API
|
||||
|
||||
### Testing
|
||||
|
||||
The `api/` tests are split into two parts:
|
||||
|
||||
1. Unit tests
|
||||
2. Integration tests
|
||||
|
||||
#### Unit Tests
|
||||
|
||||
Unit tests isolate a single function or component. The tests do not need mocking, but will require fixtures.
|
||||
|
||||
The unit tests are located in a new file adjacent the file exporting that being tested:
|
||||
|
||||
```text
|
||||
api/
|
||||
├── src/
|
||||
│ ├── utils.ts
|
||||
│ ├── utils.test.ts
|
||||
```
|
||||
|
||||
#### Integration Tests
|
||||
|
||||
Integration tests test the API as a whole. The tests will require mocking, and should not require fixtures beyond the database seeding data, and a method to authenticate.
|
||||
|
||||
Typically, each integration test file will be directly related to a route. The integration tests are located in the `api/tests/` directory:
|
||||
|
||||
```text
|
||||
api/
|
||||
├── tests/
|
||||
│ ├── settings.ts
|
||||
```
|
||||
|
||||
## Further Literature
|
||||
|
||||
- [TypeScript Docs](https://www.typescriptlang.org/docs/)
|
||||
|
||||
@@ -305,16 +305,6 @@ If you are approved, we will add you to our moderator teams on [GitHub](https://
|
||||
>
|
||||
> This is required for us to be able to give you write access to some of our repositories.
|
||||
|
||||
## How We Retire Inactive Moderators
|
||||
|
||||
Please note that we will frequently remove moderators whom we think are inactive. When we do this, we will send the following message:
|
||||
|
||||
```markdown
|
||||
This is a standard message notifying you that, since you don't seem to have been an active moderator recently, we're removing you from our moderator team. We deeply appreciate your help in the past.
|
||||
|
||||
If you think we did this in error, or once you're ready to come back and contribute more, just reply to this message letting us know.
|
||||
```
|
||||
|
||||
## How Our Contributors Room Works
|
||||
|
||||
Anyone is welcome in the [contributors room on our chat server](https://discord.gg/PRyKn3Vbay). It is the designated chat room for moderators and other campers who contribute to our community in any number of ways, including through study groups.
|
||||
@@ -488,19 +478,38 @@ If you think we're wrong in closing this issue, please request for it to be reop
|
||||
### Adding Comment About Newbie Mistakes
|
||||
|
||||
```markdown
|
||||
As a new contributor, we encourage you to read our [contributing guidelines](https://contribute.freecodecamp.org).
|
||||
Hi there,
|
||||
|
||||
We expect our contributors to be aware of the process specific to this project. Following the guidelines religiously earns you the respect of fellow maintainers and saves everyone time.
|
||||
Thanks for creating this pull request.
|
||||
|
||||
Some examples of this are:
|
||||
Please ensure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. Respect the requirements to earn the respect of your fellow maintainers. You will also save everyone time :)
|
||||
|
||||
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. Keep mentions and review requests to a minimum. We understand you are excited about contributing, and our maintainers will get back to you as soon as they get a chance.
|
||||
5. Do not work directly off your `main` branch - create a new branch for the changes you are working on.
|
||||
Since you are new here, please slow down and read our [contributing guidelines](https://contribute.freecodecamp.org), as we see that you may still need to catch up on a few things.
|
||||
|
||||
We appreciate you taking the time to help us, and we hope to see more contributions from you.
|
||||
<details>
|
||||
<summary>Here are some examples (expand)</summary>
|
||||
|
||||
1. Do not edit files directly on GitHub – while you can, it's not a good idea.
|
||||
|
||||
Typos and formatting errors can break the tests.
|
||||
|
||||
2. Use the correct way to link issues.
|
||||
|
||||
Add the issue number only in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like.
|
||||
|
||||
4. Keep mentions and review requests to a minimum.
|
||||
|
||||
We understand you are excited about contributing, and our maintainers will get back to you when they can.
|
||||
|
||||
5. Do not work directly off your `main` branch.
|
||||
|
||||
You can always create a new branch for the changes you are working on. That way, you can sync change to your PR branch as the main repository moves ahead while your PR is waiting in the merge queue.
|
||||
|
||||
</details>
|
||||
|
||||
Don't worry. You don't have to close this PR. Feel free to ask specific queries on improving your PR here; someone will guide you.
|
||||
|
||||
We are happy you are excited to contribute and appreciate you taking the time to help us. Looking forward to more contributions!
|
||||
|
||||
Happy Contributing.
|
||||
```
|
||||
|
||||
@@ -148,6 +148,40 @@ export default connect(null, mapDispatchToProps)(MyComponent);
|
||||
<!-- ### Redux Types File -->
|
||||
<!-- The types associated with the Redux store state are located in `client/src/redux/types.ts`... -->
|
||||
|
||||
## API
|
||||
|
||||
### Testing
|
||||
|
||||
The `api/` tests are split into two parts:
|
||||
|
||||
1. Unit tests
|
||||
2. Integration tests
|
||||
|
||||
#### Unit Tests
|
||||
|
||||
Unit tests isolate a single function or component. The tests do not need mocking, but will require fixtures.
|
||||
|
||||
The unit tests are located in a new file adjacent the file exporting that being tested:
|
||||
|
||||
```text
|
||||
api/
|
||||
├── src/
|
||||
│ ├── utils.ts
|
||||
│ ├── utils.test.ts
|
||||
```
|
||||
|
||||
#### Integration Tests
|
||||
|
||||
Integration tests test the API as a whole. The tests will require mocking, and should not require fixtures beyond the database seeding data, and a method to authenticate.
|
||||
|
||||
Typically, each integration test file will be directly related to a route. The integration tests are located in the `api/tests/` directory:
|
||||
|
||||
```text
|
||||
api/
|
||||
├── tests/
|
||||
│ ├── settings.ts
|
||||
```
|
||||
|
||||
## Further Literature
|
||||
|
||||
- [TypeScript Docs](https://www.typescriptlang.org/docs/)
|
||||
|
||||
@@ -305,29 +305,19 @@ If you are approved, we will add you to our moderator teams on [GitHub](https://
|
||||
>
|
||||
> This is required for us to be able to give you write access to some of our repositories.
|
||||
|
||||
## How We Retire Inactive Moderators
|
||||
|
||||
Please note that we will frequently remove moderators whom we think are inactive. When we do this, we will send the following message:
|
||||
|
||||
```markdown
|
||||
This is a standard message notifying you that, since you don't seem to have been an active moderator recently, we're removing you from our moderator team. Agradecemos profundamente tu ayuda en el pasado.
|
||||
|
||||
If you think we did this in error, or once you're ready to come back and contribute more, just reply to this message letting us know.
|
||||
```
|
||||
|
||||
## How Our Contributors Room Works
|
||||
|
||||
Anyone is welcome in the [contributors room on our chat server](https://discord.gg/PRyKn3Vbay). It is the designated chat room for moderators and other campers who contribute to our community in any number of ways, including through study groups.
|
||||
|
||||
We assume contributors will read anything in this room that directly mentions them with an **@username**. Everything else is optional, but feel free to read anything anyone posts in there and interact.
|
||||
|
||||
## Lidiando con solicitantes
|
||||
## Dealing with Solicitors
|
||||
|
||||
You may be approached by organizations who want to partner or co-brand with freeCodeCamp somehow. Once you realize that this is what they're after, **please stop talking to them** and tell them to email `team[at]freecodecamp.org`.
|
||||
|
||||
We get proposals like this all the time, and the staff are in the best position to judge whether such a relationship will be worth it for our community (and it rarely is).
|
||||
|
||||
## Tratamiento de consultas (mentales) de salud
|
||||
## Dealing with (Mental) Health Inquiries
|
||||
|
||||
You may come across situations where users seek medical advice or are dealing with mental health issues and are looking for support.
|
||||
|
||||
@@ -345,7 +335,7 @@ Helpful URLs:
|
||||
|
||||
http://suicide.org/international-suicide-hotlines.html
|
||||
|
||||
## Una nota sobre la libertad de expresión
|
||||
## A Note on Free Speech
|
||||
|
||||
Sometimes people will defend something offensive or incendiary that they said as "free speech."
|
||||
|
||||
@@ -355,7 +345,7 @@ This XKCD comic summarizes perfectly most communities' thoughts on free speech.
|
||||
|
||||
Thanks for reading this, and thanks for helping the developer community!
|
||||
|
||||
## Plantillas de Respuesta
|
||||
## Reply Templates
|
||||
|
||||
These are some of the standard reply templates that you may use while reviewing pull requests and triaging issues/pull requests.
|
||||
|
||||
@@ -364,8 +354,8 @@ These are some of the standard reply templates that you may use while reviewing
|
||||
### Thank You
|
||||
|
||||
```markdown
|
||||
Gracias por su contribución a la página! 👍
|
||||
Estamos felices de aceptar estos cambios y esperamos futuras contribuciones. 🎉
|
||||
Thank you for your contribution to the page! 👍
|
||||
We are happy to accept these changes and look forward to future contributions. 🎉
|
||||
```
|
||||
|
||||
### Thank you and congrats
|
||||
@@ -373,18 +363,24 @@ Estamos felices de aceptar estos cambios y esperamos futuras contribuciones.
|
||||
> Por dar las gracias y animar a los que han contribuido por primera vez.
|
||||
|
||||
```markdown
|
||||
Hola @nombre de usuario. ¡Felicidades por tu primer pull request (PR)! 🎉
|
||||
Hi @username. Congrats on your first pull request (PR)! 🎉
|
||||
|
||||
¡Gracias por tu contribución a la página! : Techns_up:
|
||||
Estamos encantados de aceptar estos cambios y esperamos futuras contribuciones. 📝
|
||||
Thank you for your contribution to the page! 👍
|
||||
We are happy to accept these changes and look forward to future contributions. 📝
|
||||
```
|
||||
|
||||
### Build Error
|
||||
|
||||
```markdown
|
||||
Hola @username
|
||||
Hey @username
|
||||
|
||||
Nos encantaría poder combinar tus cambios, pero parece que hay un error con la construcción de Travis CI. Una vez resueltos estos problemas, revisaremos tu PR para hacer un Merge. No dude en consultar las [pautas de contribución] (how-to-work-on-coding-challenges.md#testing-challenges) para obtener instrucciones sobre cómo ejecutar la compilación de CI localmente. ✅
|
||||
We would love to be able to merge your changes but it looks like there is an error with the CI build. ⚠️
|
||||
|
||||
Once you resolve these issues, we will be able to review your PR and merge it. 😊
|
||||
|
||||
---
|
||||
|
||||
Feel free to reference the [contributing guidelines](how-to-work-on-coding-challenges.md#testing-challenges) for instructions on running the CI build locally. ✅
|
||||
```
|
||||
|
||||
### Syncing Fork
|
||||
@@ -394,9 +390,11 @@ Nos encantaría poder combinar tus cambios, pero parece que hay un error con la
|
||||
````markdown
|
||||
Hey @username
|
||||
|
||||
Nos encantaría hacer Merge a los cambios realizados, pero parece que la rama aún no se encuentra actualizada. ⚠️Para pasar la compilación, tendrás que sincronizar los últimos cambios desde la rama master del repositorio freeCodeCamp/freeCodeCamp.
|
||||
We would love to be able to merge your changes, but it looks like the branch is not up to date. ⚠️
|
||||
|
||||
Usando la línea de comando, puede hacer esto en tres sencillos pasos:
|
||||
To resolve this error, you will have to sync the latest changes from the `main` branch of the `freeCodeCamp/freeCodeCamp` repo.
|
||||
|
||||
Using the command line, you can do this in three easy steps:
|
||||
|
||||
```bash
|
||||
git remote add upstream git://github.com/freeCodeCamp/freeCodeCamp.git
|
||||
@@ -415,18 +413,22 @@ Once you sync your fork and pass the build, we will be able to review your PR an
|
||||
Feel free to reference the ["Syncing a fork"](https://help.github.com/articles/syncing-a-fork/) article on GitHub for more insight on how to keep your fork up-to-date with the upstream repository. 🔄
|
||||
````
|
||||
|
||||
### Fusionar conflictos
|
||||
### Merge Conflicts
|
||||
|
||||
> Cuando las PR tienen conflictos que necesitan ser resueltos.1
|
||||
> When PR has merge conflicts that need to be resolved.¹
|
||||
|
||||
```markdown
|
||||
Hey @username
|
||||
|
||||
Nos encantaría poder fusionar sus cambios, pero parece que tiene algunos conflictos de fusion. Una vez que resuelva estos conflictos, podremos revisar su RP y fusionarlo. 😊
|
||||
We would love to be able to merge your changes, but it looks like you have some merge conflicts. ⚠️
|
||||
|
||||
Once you resolve these conflicts, we will be able to review your PR and merge it. 😊
|
||||
|
||||
---
|
||||
|
||||
Si no estás familiarizado con el proceso de fusión de conflictos, no dudes en echar un vistazo a la guía de GitHub en ["Resolviendo un conflicto de fusiones"](https://help. ithub.com/articles/resolving-a-merge-conflict-on-github/). 🔍️
|
||||
If you're not familiar with the merge conflict process, feel free to look over GitHub's guide on ["Resolving a merge conflict"](https://help.github.com/articles/resolving-a-merge-conflict-on-github/). 🔍️
|
||||
|
||||
Además, es buena práctica en GitHub escribir una breve descripción de los cambios al crear un PR. 📝
|
||||
Also, it's good practice on GitHub to write a brief description of your changes when creating a PR. 📝
|
||||
````
|
||||
|
||||
¹ If a first-time-contributor has a merge conflict, maintainers will resolve the conflict for them.
|
||||
@@ -436,19 +438,17 @@ Nos encantaría poder fusionar sus cambios, pero parece que tiene algunos confli
|
||||
> When PR is repetitive or a duplicate.
|
||||
|
||||
```markdown
|
||||
Hola @nombredeusuario
|
||||
Hey @username
|
||||
|
||||
Este RP parece realizar cambios similares a los del RP existente & lt; # number & gt .
|
||||
This PR seems to make similar changes as the existing PR <#number>. As such, we are going to close this as a duplicate.
|
||||
|
||||
As such, we are going to close this as a duplicate.
|
||||
If you feel you have additional changes to expand upon this PR, please feel free to push your commits and request this PR be reopened.
|
||||
|
||||
Si cree que tiene cambios adicionales para expandir este PR, no dude en presionar sus confirmaciones y solicitar que este PR se vuelva a abrir.
|
||||
|
||||
¡Gracias de nuevo! 😊
|
||||
Thanks again! 😊
|
||||
|
||||
---
|
||||
|
||||
Si tienes alguna pregunta, no dudes en hacer preguntas en la categoría ["Colaboradores" en nuestro foro](https://forum.freecodecamp.org/c/contributors) o [la sala de chat de colaboradores](https://discord.gg/PRyKn3Vbay).
|
||||
If you have any questions, feel free to ask questions on the ["Contributors" category on our forum](https://forum.freecodecamp.org/c/contributors) or [the contributors chat room](https://discord.gg/PRyKn3Vbay).
|
||||
```
|
||||
|
||||
### Closing Invalid Pull Requests
|
||||
@@ -456,41 +456,60 @@ Si tienes alguna pregunta, no dudes en hacer preguntas en la categoría ["Colabo
|
||||
> When PR is invalid.
|
||||
|
||||
```markdown
|
||||
Hola @username
|
||||
Hey @username
|
||||
|
||||
Gracias por abrir este pull request.
|
||||
Thank you for opening this pull request.
|
||||
|
||||
Este es un mensaje estándar notificándole que hemos revisado su pull request y hemos decidido no fusionarlo. Damos la bienvenida a tus futuras pull request.
|
||||
This is a standard message notifying you that we've reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
|
||||
|
||||
Gracias y ten un feliz día programando.
|
||||
Thank you and happy coding.
|
||||
```
|
||||
|
||||
> When PR adds links to external resources.
|
||||
|
||||
```markdown
|
||||
Gracias por abrir esta solicitud de extracción.
|
||||
Thank you for your pull request.
|
||||
|
||||
Cerramos esta solicitud de extracción. Sugiera enlaces y otros detalles para agregar la publicación de la guía correspondiente al desafío a través de [un tema del foro] (https://forum.freecodecamp.org/new-topic?category=Contributors&title=&body=**What%20is% 20su% 20sugestión% 20o% 20solución% 20sugerencia% 3F **% 0A% 0A% 0A% 0A% 0A ** Desafío% 3A **% 0A% 0A% 0A ** Vínculo% 20a% 20el% 20 desafío% 3A **) en lugar de.
|
||||
We are closing this pull request. Please suggest links and other details to add the challenge's corresponding guide post through [a forum topic](https://forum.freecodecamp.org/new-topic?category=Contributors&title=&body=**What%20is%20your%20hint%20or%20solution%20suggestion%3F**%0A%0A%0A%0A%0A**Challenge%3A**%0A%0A%0A**Link%20to%20the%20challenge%3A**) instead.
|
||||
|
||||
Si consideras que nos hemos equivocado cerrando esta incidencia, por favor solicita su reapertura y añade más aclaraciones. Thank you and happy coding.
|
||||
If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding.
|
||||
```
|
||||
|
||||
### Adding Comment About Newbie Mistakes
|
||||
|
||||
```markdown
|
||||
As a new contributor, we encourage you to read our [contributing guidelines](https://contribute.freecodecamp.org).
|
||||
Hi there,
|
||||
|
||||
We expect our contributors to be aware of the process specific to this project. Following the guidelines religiously earns you the respect of fellow maintainers and saves everyone time.
|
||||
Thanks for creating this pull request.
|
||||
|
||||
Some examples of this are:
|
||||
Please ensure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. Respect the requirements to earn the respect of your fellow maintainers. You will also save everyone time :)
|
||||
|
||||
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. Keep mentions and review requests to a minimum. We understand you are excited about contributing, and our maintainers will get back to you as soon as they get a chance.
|
||||
5. Do not work directly off your `main` branch - create a new branch for the changes you are working on.
|
||||
Since you are new here, please slow down and read our [contributing guidelines](https://contribute.freecodecamp.org), as we see that you may still need to catch up on a few things.
|
||||
|
||||
We appreciate you taking the time to help us, and we hope to see more contributions from you.
|
||||
<details>
|
||||
<summary>Here are some examples (expand)</summary>
|
||||
|
||||
1. Do not edit files directly on GitHub – while you can, it's not a good idea.
|
||||
|
||||
Typos and formatting errors can break the tests.
|
||||
|
||||
2. Use the correct way to link issues.
|
||||
|
||||
Add the issue number only in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like.
|
||||
|
||||
4. Keep mentions and review requests to a minimum.
|
||||
|
||||
We understand you are excited about contributing, and our maintainers will get back to you when they can.
|
||||
|
||||
5. Do not work directly off your `main` branch.
|
||||
|
||||
You can always create a new branch for the changes you are working on. That way, you can sync change to your PR branch as the main repository moves ahead while your PR is waiting in the merge queue.
|
||||
|
||||
</details>
|
||||
|
||||
Don't worry. You don't have to close this PR. Feel free to ask specific queries on improving your PR here; someone will guide you.
|
||||
|
||||
We are happy you are excited to contribute and appreciate you taking the time to help us. Looking forward to more contributions!
|
||||
|
||||
Happy Contributing.
|
||||
```
|
||||
@@ -500,7 +519,7 @@ Happy Contributing.
|
||||
> When an issue relates to the camper's code.
|
||||
|
||||
```markdown
|
||||
Gracias por reportar este problema.
|
||||
Thank you for reporting this issue.
|
||||
|
||||
This is a standard message notifying you that this issue seems to be a request for help. Instead of asking for help here, please click the **"Get Help"** button on the challenge on freeCodeCamp and choose the **"Ask for help"** option, which will help you create a question in the right part of the forum. Volunteers on the forum usually respond to questions within a few hours and can help determine if there is an issue with your code or the challenge's tests.
|
||||
|
||||
@@ -512,7 +531,7 @@ Thank you and happy coding.
|
||||
> When an issue is duplicate of an earlier issue.
|
||||
|
||||
```markdown
|
||||
Gracias por reportar elproblema.
|
||||
Gracias por reportar este problema.
|
||||
|
||||
This is a standard message notifying you that this issue appears to be very similar to issue #XXXXX, so we are closing it as a duplicate.
|
||||
|
||||
@@ -522,7 +541,7 @@ If you think we're wrong in closing this issue, please request for it to be reop
|
||||
> When an issue is fixed in staging.
|
||||
|
||||
```markdown
|
||||
Thank you for reporting this issue.
|
||||
Gracias por reportar elproblema.
|
||||
|
||||
This is a standard message notifying you that the problem you mentioned here is present in production, but that it has already been fixed in staging. This means that the next time we push our staging branch to production, this problem should be fixed. Because of this, we're closing this issue.
|
||||
|
||||
|
||||
@@ -148,6 +148,40 @@ export default connect(null, mapDispatchToProps)(MyComponent);
|
||||
<!-- ### Redux Types File -->
|
||||
<!-- The types associated with the Redux store state are located in `client/src/redux/types.ts`... -->
|
||||
|
||||
## API
|
||||
|
||||
### Testing
|
||||
|
||||
The `api/` tests are split into two parts:
|
||||
|
||||
1. Unit tests
|
||||
2. Integration tests
|
||||
|
||||
#### Unit Tests
|
||||
|
||||
Unit tests isolate a single function or component. The tests do not need mocking, but will require fixtures.
|
||||
|
||||
The unit tests are located in a new file adjacent the file exporting that being tested:
|
||||
|
||||
```text
|
||||
api/
|
||||
├── src/
|
||||
│ ├── utils.ts
|
||||
│ ├── utils.test.ts
|
||||
```
|
||||
|
||||
#### Integration Tests
|
||||
|
||||
Integration tests test the API as a whole. The tests will require mocking, and should not require fixtures beyond the database seeding data, and a method to authenticate.
|
||||
|
||||
Typically, each integration test file will be directly related to a route. The integration tests are located in the `api/tests/` directory:
|
||||
|
||||
```text
|
||||
api/
|
||||
├── tests/
|
||||
│ ├── settings.ts
|
||||
```
|
||||
|
||||
## Further Literature
|
||||
|
||||
- [TypeScript Docs](https://www.typescriptlang.org/docs/)
|
||||
|
||||
@@ -305,16 +305,6 @@ If you are approved, we will add you to our moderator teams on [GitHub](https://
|
||||
>
|
||||
> This is required for us to be able to give you write access to some of our repositories.
|
||||
|
||||
## How We Retire Inactive Moderators
|
||||
|
||||
Please note that we will frequently remove moderators whom we think are inactive. When we do this, we will send the following message:
|
||||
|
||||
```markdown
|
||||
This is a standard message notifying you that, since you don't seem to have been an active moderator recently, we're removing you from our moderator team. We deeply appreciate your help in the past.
|
||||
|
||||
If you think we did this in error, or once you're ready to come back and contribute more, just reply to this message letting us know.
|
||||
```
|
||||
|
||||
## How Our Contributors Room Works
|
||||
|
||||
Anyone is welcome in the [contributors room on our chat server](https://discord.gg/PRyKn3Vbay). It is the designated chat room for moderators and other campers who contribute to our community in any number of ways, including through study groups.
|
||||
@@ -355,7 +345,7 @@ This XKCD comic summarizes perfectly most communities' thoughts on free speech.
|
||||
|
||||
Thanks for reading this, and thanks for helping the developer community!
|
||||
|
||||
## Antwortvorlagen
|
||||
## Reply Templates
|
||||
|
||||
These are some of the standard reply templates that you may use while reviewing pull requests and triaging issues/pull requests.
|
||||
|
||||
@@ -438,7 +428,7 @@ Once you resolve these conflicts, we will be able to review your PR and merge it
|
||||
|
||||
If you're not familiar with the merge conflict process, feel free to look over GitHub's guide on ["Resolving a merge conflict"](https://help.github.com/articles/resolving-a-merge-conflict-on-github/). 🔍️
|
||||
|
||||
Dit is ook goeie praktyk op GitHub om 'n kort beskrywing van jou veranderinge te skryf wanneer jy 'n PR skep. 📝
|
||||
Also, it's good practice on GitHub to write a brief description of your changes when creating a PR. 📝
|
||||
````
|
||||
|
||||
¹ If a first-time-contributor has a merge conflict, maintainers will resolve the conflict for them.
|
||||
@@ -488,19 +478,38 @@ If you think we're wrong in closing this issue, please request for it to be reop
|
||||
### Adding Comment About Newbie Mistakes
|
||||
|
||||
```markdown
|
||||
As a new contributor, we encourage you to read our [contributing guidelines](https://contribute.freecodecamp.org).
|
||||
Hi there,
|
||||
|
||||
We expect our contributors to be aware of the process specific to this project. Following the guidelines religiously earns you the respect of fellow maintainers and saves everyone time.
|
||||
Thanks for creating this pull request.
|
||||
|
||||
Some examples of this are:
|
||||
Please ensure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. Respect the requirements to earn the respect of your fellow maintainers. You will also save everyone time :)
|
||||
|
||||
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. Keep mentions and review requests to a minimum. We understand you are excited about contributing, and our maintainers will get back to you as soon as they get a chance.
|
||||
5. Do not work directly off your `main` branch - create a new branch for the changes you are working on.
|
||||
Since you are new here, please slow down and read our [contributing guidelines](https://contribute.freecodecamp.org), as we see that you may still need to catch up on a few things.
|
||||
|
||||
We appreciate you taking the time to help us, and we hope to see more contributions from you.
|
||||
<details>
|
||||
<summary>Here are some examples (expand)</summary>
|
||||
|
||||
1. Do not edit files directly on GitHub – while you can, it's not a good idea.
|
||||
|
||||
Typos and formatting errors can break the tests.
|
||||
|
||||
2. Use the correct way to link issues.
|
||||
|
||||
Add the issue number only in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like.
|
||||
|
||||
4. Keep mentions and review requests to a minimum.
|
||||
|
||||
We understand you are excited about contributing, and our maintainers will get back to you when they can.
|
||||
|
||||
5. Do not work directly off your `main` branch.
|
||||
|
||||
You can always create a new branch for the changes you are working on. That way, you can sync change to your PR branch as the main repository moves ahead while your PR is waiting in the merge queue.
|
||||
|
||||
</details>
|
||||
|
||||
Don't worry. You don't have to close this PR. Feel free to ask specific queries on improving your PR here; someone will guide you.
|
||||
|
||||
We are happy you are excited to contribute and appreciate you taking the time to help us. Looking forward to more contributions!
|
||||
|
||||
Happy Contributing.
|
||||
```
|
||||
|
||||
@@ -148,7 +148,41 @@ export default connect(null, mapDispatchToProps)(MyComponent);
|
||||
<!-- ### Redux Types File -->
|
||||
<!-- The types associated with the Redux store state are located in `client/src/redux/types.ts`... -->
|
||||
|
||||
## Letture aggiuntive
|
||||
## API
|
||||
|
||||
### Testing
|
||||
|
||||
The `api/` tests are split into two parts:
|
||||
|
||||
1. Unit tests
|
||||
2. Integration tests
|
||||
|
||||
#### Unit Tests
|
||||
|
||||
Unit tests isolate a single function or component. The tests do not need mocking, but will require fixtures.
|
||||
|
||||
The unit tests are located in a new file adjacent the file exporting that being tested:
|
||||
|
||||
```text
|
||||
api/
|
||||
├── src/
|
||||
│ ├── utils.ts
|
||||
│ ├── utils.test.ts
|
||||
```
|
||||
|
||||
#### Integration Tests
|
||||
|
||||
Integration tests test the API as a whole. The tests will require mocking, and should not require fixtures beyond the database seeding data, and a method to authenticate.
|
||||
|
||||
Typically, each integration test file will be directly related to a route. The integration tests are located in the `api/tests/` directory:
|
||||
|
||||
```text
|
||||
api/
|
||||
├── tests/
|
||||
│ ├── settings.ts
|
||||
```
|
||||
|
||||
## Further Literature
|
||||
|
||||
- [Documentazione di TypeScript](https://www.typescriptlang.org/docs/)
|
||||
- [CheatSheet di TypeScript con React](https://github.com/typescript-cheatsheets/react#readme)
|
||||
|
||||
@@ -305,67 +305,57 @@ Se verrai approvato, ti aggiungeremo al nostro Team dei Moderatori su [GitHub](h
|
||||
>
|
||||
> Questo è necessario per consentirci di darti i permessi di scrittura su alcuni dei nostri repository.
|
||||
|
||||
## Come congediamo i moderatori inattivi
|
||||
## How Our Contributors Room Works
|
||||
|
||||
Per favore, nota che rimuoviamo frequentemente i moderatori che riteniamo essere inattivi. Quando lo facciamo, inviamo il seguente messaggio:
|
||||
Anyone is welcome in the [contributors room on our chat server](https://discord.gg/PRyKn3Vbay). It is the designated chat room for moderators and other campers who contribute to our community in any number of ways, including through study groups.
|
||||
|
||||
```markdown
|
||||
This is a standard message notifying you that, since you don't seem to have been an active moderator recently, we're removing you from our Moderator team. We deeply appreciate your help in the past.
|
||||
We assume contributors will read anything in this room that directly mentions them with an **@username**. Everything else is optional, but feel free to read anything anyone posts in there and interact.
|
||||
|
||||
If you think we did this in error, or once you're ready to come back and contribute more, just reply to this message letting us know.
|
||||
```
|
||||
## Dealing with Solicitors
|
||||
|
||||
## Come funzionano le stanze dei contributori
|
||||
You may be approached by organizations who want to partner or co-brand with freeCodeCamp somehow. Once you realize that this is what they're after, **please stop talking to them** and tell them to email `team[at]freecodecamp.org`.
|
||||
|
||||
Chiunque è il benvenuto nella [stanza dei contributori sul nostro server di chat](https://discord.gg/PRyKn3Vbay). È la chat room designata per i moderatori e per gli utenti che contribuiscono alla nostra comunità in altri modi, anche attraverso i gruppi di studio.
|
||||
We get proposals like this all the time, and the staff are in the best position to judge whether such a relationship will be worth it for our community (and it rarely is).
|
||||
|
||||
Diamo per assodato che i contributori leggano qualunque messaggio in cui siano nominati direttamente con **@username**. Tutto il resto è opzionale, ma sentiti libero di leggere qualunque cosa venga postata da chiunque, e interagire.
|
||||
## Dealing with (Mental) Health Inquiries
|
||||
|
||||
## Affrontare i sollecitatori
|
||||
You may come across situations where users seek medical advice or are dealing with mental health issues and are looking for support.
|
||||
|
||||
Potresti essere avvicinato da organizzazioni che vogliono collaborare o diventare un co-brand di freeCodeCamp in qualche modo. Una volta che ti sei reso conto che questo è ciò che vogliono, **smetti di parlare con loro** e di' loro di mandare una email a `team[at]freecodecamp.org`.
|
||||
As a matter of policy, you should avoid talking privately about these matters. Should the situation reflect back to freeCodeCamp, we want to have the conversation(s) on record. Make it clear that we are not medical professionals and that you encourage the user to find professional help.
|
||||
|
||||
Riceviamo proposte del genere continuamente e lo staff è nella posizione migliore per giudicare se valga la pena che la comunità intraprenda queste relazioni (cosa che succede raramente).
|
||||
As difficult as it sometimes can be, avoid giving any tips or advice and rather point the user in the direction of seeking professional help!
|
||||
|
||||
## Affrontare richieste sulla salute (mentale)
|
||||
|
||||
Potresti incontrare situazioni in cui gli utenti ricercano consigli medici o stanno affrontando problemi di salute mentale e cercano supporto.
|
||||
|
||||
Per una questione di principio, dovesti evitare di parlare di questi temi privatamente. Se la situazione dovesse riflettersi su freeCodeCamp, vogliamo che le conversazioni siano registrate. Chiarisci che non siamo medici professionisti e incoraggia l'utente a cercare aiuto professionale.
|
||||
|
||||
Per quanto a volte sia difficile, evita di dare suggerimenti o consigli diversi dall'indirizzare l'utente verso l'aiuto professionale!
|
||||
|
||||
Se questo accade sul server delle chat: crea un canale privato per l'utente e il team dei moderatori. Questo può essere fatto con il comando `private` del bot.
|
||||
If this happens on our chat server: Create a private channel for the user and the moderator team. This can be done with the bot's `private` command.
|
||||
|
||||
- All'utente viene garantita privacy.
|
||||
- La chat pubblica non è più interrotta.
|
||||
- Altri membri del team possono contribuire, nel caso tu sia a disagio nell'affrontare la situazione da solo.
|
||||
|
||||
URL utili:
|
||||
Helpful URLs:
|
||||
|
||||
http://suicide.org/international-suicide-hotlines.html
|
||||
|
||||
## Una nota sulla libertà di parola
|
||||
## A Note on Free Speech
|
||||
|
||||
A volte le persone difenderanno qualcosa di offensivo o aggressivo che hanno detto, come "libertà di parola."
|
||||
Sometimes people will defend something offensive or incendiary that they said as "free speech."
|
||||
|
||||
Questo fumetto di XKCD riassume perfettamente il pensiero di molte comunità a proposito della libertà di parola.
|
||||
This XKCD comic summarizes perfectly most communities' thoughts on free speech.
|
||||
|
||||
<div align="center"><img src='./images/github/xkcd-free-speech.png' width="400" height="400" /></div>
|
||||
|
||||
Grazie per aver letto e grazie per l'aiuto alla comunità degli sviluppatori!
|
||||
Thanks for reading this, and thanks for helping the developer community!
|
||||
|
||||
## Modelli di risposta
|
||||
## Reply Templates
|
||||
|
||||
Queste sono alcune delle risposte standard che potresti voler usare mentre verifichi le pull request e fai il triage delle issue e delle pull request.
|
||||
These are some of the standard reply templates that you may use while reviewing pull requests and triaging issues/pull requests.
|
||||
|
||||
> Puoi creare le tue con la feature integrata di GitHub [saved replies](https://github.com/settings/replies/) oppure utilizzare quelle qui sotto.
|
||||
|
||||
### Ringraziamenti
|
||||
|
||||
```markdown
|
||||
Thank you for your contribution to the page! We are happy to accept these changes and look forward to future contributions. 🎉.
|
||||
🎉
|
||||
Thank you for your contribution to the page! 👍
|
||||
We are happy to accept these changes and look forward to future contributions. 🎉
|
||||
```
|
||||
|
||||
### Ringraziamenti e congratulazioni
|
||||
@@ -404,7 +394,7 @@ We would love to be able to merge your changes, but it looks like the branch is
|
||||
|
||||
To resolve this error, you will have to sync the latest changes from the `main` branch of the `freeCodeCamp/freeCodeCamp` repo.
|
||||
|
||||
Usando il terminale, puoi farlo in tre facili step:
|
||||
Using the command line, you can do this in three easy steps:
|
||||
|
||||
```bash
|
||||
git remote add upstream git://github.com/freeCodeCamp/freeCodeCamp.git
|
||||
@@ -414,18 +404,18 @@ git fetch upstream
|
||||
git pull upstream main
|
||||
````
|
||||
|
||||
Se stai usando una GUI, puoi semplicemente cercare il comando `Add a new remote...` e usare il link `git://github.com/freeCodeCamp/freeCodeCamp.git` visto sopra.
|
||||
If you're using a GUI, you can simply `Add a new remote...` and use the link `git://github.com/freeCodeCamp/freeCodeCamp.git` from above.
|
||||
|
||||
Una volta che avrai sincronizzato il fork e superato il build, saremo in grado di rivedere la tua PR e farne il merge. 😊
|
||||
Once you sync your fork and pass the build, we will be able to review your PR and merge it. 😊
|
||||
|
||||
---
|
||||
|
||||
Sentiti libero di fare riferimento all'articolo [Sincronizzare un fork](https://help.github.com/articles/syncing-a-fork/) su GitHub per ulteriori informazioni su come mantenere aggiornato il fork con il repository di upstream. 🔄
|
||||
Feel free to reference the ["Syncing a fork"](https://help.github.com/articles/syncing-a-fork/) article on GitHub for more insight on how to keep your fork up-to-date with the upstream repository. 🔄
|
||||
````
|
||||
|
||||
### Conflitti in fase di merge
|
||||
### Merge Conflicts
|
||||
|
||||
> Quando una PR ha dei conflitti di fusione che devono essere risolti.¹
|
||||
> When PR has merge conflicts that need to be resolved.¹
|
||||
|
||||
```markdown
|
||||
Hey @username
|
||||
@@ -441,7 +431,7 @@ If you're not familiar with the merge conflict process, feel free to look over G
|
||||
Also, it's good practice on GitHub to write a brief description of your changes when creating a PR. 📝
|
||||
````
|
||||
|
||||
¹ Se una persona che contribuisce per la prima volta ha un conflitto di merge, i manutentori risolveranno il conflitto per lui.
|
||||
¹ If a first-time-contributor has a merge conflict, maintainers will resolve the conflict for them.
|
||||
|
||||
### Duplicati
|
||||
|
||||
@@ -458,7 +448,7 @@ Thanks again! 😊
|
||||
|
||||
---
|
||||
|
||||
If you have any questions, feel free to ask questions on the ['Contributors' category on our forum](https://forum.freecodecamp.org/c/contributors) or [the contributors chat room](https://discord.gg/PRyKn3Vbay).
|
||||
If you have any questions, feel free to ask questions on the ["Contributors" category on our forum](https://forum.freecodecamp.org/c/contributors) or [the contributors chat room](https://discord.gg/PRyKn3Vbay).
|
||||
```
|
||||
|
||||
### Chiudere le pull request non valide
|
||||
@@ -488,19 +478,38 @@ If you think we're wrong in closing this issue, please request for it to be reop
|
||||
### Adding Comment About Newbie Mistakes
|
||||
|
||||
```markdown
|
||||
As a new contributor, we encourage you to read our [contributing guidelines](https://contribute.freecodecamp.org).
|
||||
Hi there,
|
||||
|
||||
We expect our contributors to be aware of the process specific to this project. Following the guidelines religiously earns you the respect of fellow maintainers and saves everyone time.
|
||||
Thanks for creating this pull request.
|
||||
|
||||
Some examples of this are:
|
||||
Please ensure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. Respect the requirements to earn the respect of your fellow maintainers. You will also save everyone time :)
|
||||
|
||||
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. Keep mentions and review requests to a minimum. We understand you are excited about contributing, and our maintainers will get back to you as soon as they get a chance.
|
||||
5. Do not work directly off your `main` branch - create a new branch for the changes you are working on.
|
||||
Since you are new here, please slow down and read our [contributing guidelines](https://contribute.freecodecamp.org), as we see that you may still need to catch up on a few things.
|
||||
|
||||
We appreciate you taking the time to help us, and we hope to see more contributions from you.
|
||||
<details>
|
||||
<summary>Here are some examples (expand)</summary>
|
||||
|
||||
1. Do not edit files directly on GitHub – while you can, it's not a good idea.
|
||||
|
||||
Typos and formatting errors can break the tests.
|
||||
|
||||
2. Use the correct way to link issues.
|
||||
|
||||
Add the issue number only in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like.
|
||||
|
||||
4. Keep mentions and review requests to a minimum.
|
||||
|
||||
We understand you are excited about contributing, and our maintainers will get back to you when they can.
|
||||
|
||||
5. Do not work directly off your `main` branch.
|
||||
|
||||
You can always create a new branch for the changes you are working on. That way, you can sync change to your PR branch as the main repository moves ahead while your PR is waiting in the merge queue.
|
||||
|
||||
</details>
|
||||
|
||||
Don't worry. You don't have to close this PR. Feel free to ask specific queries on improving your PR here; someone will guide you.
|
||||
|
||||
We are happy you are excited to contribute and appreciate you taking the time to help us. Looking forward to more contributions!
|
||||
|
||||
Happy Contributing.
|
||||
```
|
||||
|
||||
@@ -148,6 +148,40 @@ export default connect(null, mapDispatchToProps)(MyComponent);
|
||||
<!-- ### Redux Types File -->
|
||||
<!-- The types associated with the Redux store state are located in `client/src/redux/types.ts`... -->
|
||||
|
||||
## API
|
||||
|
||||
### Testing
|
||||
|
||||
The `api/` tests are split into two parts:
|
||||
|
||||
1. Unit tests
|
||||
2. Integration tests
|
||||
|
||||
#### Unit Tests
|
||||
|
||||
Unit tests isolate a single function or component. The tests do not need mocking, but will require fixtures.
|
||||
|
||||
The unit tests are located in a new file adjacent the file exporting that being tested:
|
||||
|
||||
```text
|
||||
api/
|
||||
├── src/
|
||||
│ ├── utils.ts
|
||||
│ ├── utils.test.ts
|
||||
```
|
||||
|
||||
#### Integration Tests
|
||||
|
||||
Integration tests test the API as a whole. The tests will require mocking, and should not require fixtures beyond the database seeding data, and a method to authenticate.
|
||||
|
||||
Typically, each integration test file will be directly related to a route. The integration tests are located in the `api/tests/` directory:
|
||||
|
||||
```text
|
||||
api/
|
||||
├── tests/
|
||||
│ ├── settings.ts
|
||||
```
|
||||
|
||||
## Further Literature
|
||||
|
||||
- [TypeScript Docs](https://www.typescriptlang.org/docs/)
|
||||
|
||||
@@ -305,16 +305,6 @@ If you are approved, we will add you to our moderator teams on [GitHub](https://
|
||||
>
|
||||
> This is required for us to be able to give you write access to some of our repositories.
|
||||
|
||||
## How We Retire Inactive Moderators
|
||||
|
||||
Please note that we will frequently remove moderators whom we think are inactive. When we do this, we will send the following message:
|
||||
|
||||
```markdown
|
||||
This is a standard message notifying you that, since you don't seem to have been an active moderator recently, we're removing you from our moderator team. これまでのご支援に深く感謝いたします。
|
||||
|
||||
If you think we did this in error, or once you're ready to come back and contribute more, just reply to this message letting us know.
|
||||
```
|
||||
|
||||
## How Our Contributors Room Works
|
||||
|
||||
Anyone is welcome in the [contributors room on our chat server](https://discord.gg/PRyKn3Vbay). It is the designated chat room for moderators and other campers who contribute to our community in any number of ways, including through study groups.
|
||||
@@ -355,7 +345,7 @@ This XKCD comic summarizes perfectly most communities' thoughts on free speech.
|
||||
|
||||
Thanks for reading this, and thanks for helping the developer community!
|
||||
|
||||
## 返信テンプレート
|
||||
## Reply Templates
|
||||
|
||||
These are some of the standard reply templates that you may use while reviewing pull requests and triaging issues/pull requests.
|
||||
|
||||
@@ -423,9 +413,9 @@ Once you sync your fork and pass the build, we will be able to review your PR an
|
||||
Feel free to reference the ["Syncing a fork"](https://help.github.com/articles/syncing-a-fork/) article on GitHub for more insight on how to keep your fork up-to-date with the upstream repository. 🔄
|
||||
````
|
||||
|
||||
### マージ競合
|
||||
### Merge Conflicts
|
||||
|
||||
> PR に解決すべきマージ競合がある場合¹
|
||||
> When PR has merge conflicts that need to be resolved.¹
|
||||
|
||||
```markdown
|
||||
Hey @username
|
||||
@@ -488,19 +478,38 @@ If you think we're wrong in closing this issue, please request for it to be reop
|
||||
### Adding Comment About Newbie Mistakes
|
||||
|
||||
```markdown
|
||||
As a new contributor, we encourage you to read our [contributing guidelines](https://contribute.freecodecamp.org).
|
||||
Hi there,
|
||||
|
||||
We expect our contributors to be aware of the process specific to this project. Following the guidelines religiously earns you the respect of fellow maintainers and saves everyone time.
|
||||
Thanks for creating this pull request.
|
||||
|
||||
Some examples of this are:
|
||||
Please ensure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. Respect the requirements to earn the respect of your fellow maintainers. You will also save everyone time :)
|
||||
|
||||
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. Keep mentions and review requests to a minimum. We understand you are excited about contributing, and our maintainers will get back to you as soon as they get a chance.
|
||||
5. Do not work directly off your `main` branch - create a new branch for the changes you are working on.
|
||||
Since you are new here, please slow down and read our [contributing guidelines](https://contribute.freecodecamp.org), as we see that you may still need to catch up on a few things.
|
||||
|
||||
We appreciate you taking the time to help us, and we hope to see more contributions from you.
|
||||
<details>
|
||||
<summary>Here are some examples (expand)</summary>
|
||||
|
||||
1. Do not edit files directly on GitHub – while you can, it's not a good idea.
|
||||
|
||||
Typos and formatting errors can break the tests.
|
||||
|
||||
2. Use the correct way to link issues.
|
||||
|
||||
Add the issue number only in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like.
|
||||
|
||||
4. Keep mentions and review requests to a minimum.
|
||||
|
||||
We understand you are excited about contributing, and our maintainers will get back to you when they can.
|
||||
|
||||
5. Do not work directly off your `main` branch.
|
||||
|
||||
You can always create a new branch for the changes you are working on. That way, you can sync change to your PR branch as the main repository moves ahead while your PR is waiting in the merge queue.
|
||||
|
||||
</details>
|
||||
|
||||
Don't worry. You don't have to close this PR. Feel free to ask specific queries on improving your PR here; someone will guide you.
|
||||
|
||||
We are happy you are excited to contribute and appreciate you taking the time to help us. Looking forward to more contributions!
|
||||
|
||||
Happy Contributing.
|
||||
```
|
||||
|
||||
@@ -148,6 +148,40 @@ export default connect(null, mapDispatchToProps)(MyComponent);
|
||||
<!-- ### Redux Types File -->
|
||||
<!-- The types associated with the Redux store state are located in `client/src/redux/types.ts`... -->
|
||||
|
||||
## API
|
||||
|
||||
### Testes
|
||||
|
||||
Os testes `api/` são divididos em duas partes:
|
||||
|
||||
1. Teste de unidade
|
||||
2. Testes de integração
|
||||
|
||||
#### Teste de unidade
|
||||
|
||||
Testes de unidade isolam uma única função ou componente. Os testes não precisam de simulação (mocking, em inglês), mas exigirão instalações.
|
||||
|
||||
Os testes de unidade estão localizados em um novo arquivo adjacente ao arquivo que exporta que está sendo testado:
|
||||
|
||||
```text
|
||||
api/
|
||||
├── src/
|
||||
│ ├── utils.ts
|
||||
│ ├── utils.test.ts
|
||||
```
|
||||
|
||||
#### Testes de integração
|
||||
|
||||
Testes de integração testam a API como um todo. Os testes exigirão simulação (mocking, em inglês) e não devem exigir fixtures além dos dados de semeamento (seeding) de banco de dados e um método para autenticar.
|
||||
|
||||
Normalmente, cada arquivo de teste de integração estará diretamente relacionado a uma rota. Os testes de integração estão localizados no diretório `api/tests/`:
|
||||
|
||||
```text
|
||||
api/
|
||||
├── tests/
|
||||
│ ├── settings.ts
|
||||
```
|
||||
|
||||
## Mais informações
|
||||
|
||||
- [Documentação do TypeScript](https://www.typescriptlang.org/docs/)
|
||||
|
||||
@@ -305,16 +305,6 @@ Se for aprovado, nós adicionaremos você ao nosso time de moderadores no [GitHu
|
||||
>
|
||||
> Isso é necessário para nós podermos dar a você acesso de escrita em alguns de nossos repositórios.
|
||||
|
||||
## Como nós retiramos moderadores inativos
|
||||
|
||||
Observe que, frequentemente, removeremos moderadores que pensamos estarem inativos. Quando fizermos isso, enviaremos a seguinte mensagem:
|
||||
|
||||
```markdown
|
||||
Essa é uma mensagem padrão notificando que você não parece ter sido um moderador ativo recentemente. Sendo assim, estamos removendo você do nosso time de moderadores. Nós agradecemos profundamente sua ajuda no passado.
|
||||
|
||||
Se acha que fizemos isso por engano ou quando você estiver pronto para voltar e contribuir mais, apenas responda essa mensagem nos avisando.
|
||||
```
|
||||
|
||||
## Como funciona nossa sala de Colaboradores
|
||||
|
||||
Todos são bem-vindos no [chat de colaboradores do nosso servidor](https://discord.gg/PRyKn3Vbay). Esse é o chat destinado aos moderadores e outros usuários do freeCodeCamp que estão contribuindo para nossa comunidade de diversas formas, incluindo através de grupos de estudo.
|
||||
@@ -331,17 +321,17 @@ Recebemos propostas como essa com frequência. A equipe está em melhor posiçã
|
||||
|
||||
Você pode encontrar situações onde os usuários procuram aconselhamento médico ou estão lidando com questões de saúde mental e buscando apoio.
|
||||
|
||||
Como parte de nossa política, você deve evitar falar em privado sobre essas questões. Se a situação em algum ponto refletir o freeCodeCamp, queremos que as conversas fiquem registradas. Deixe claro que não somos profissionais da medicina e que você encoraja o usuário a procurar ajuda profissional.
|
||||
Como parte de nossa política, você deve evitar falar em privado sobre essas questões. Se a situação em algum ponto refletir de volta para o freeCodeCamp, queremos que as conversas fiquem registradas. Deixe claro que nós não somos profissionais da saúde e que você encoraja o usuário a buscar ajuda profissional.
|
||||
|
||||
Apesar de ser difícil às vezes, evite dar quaisquer dicas ou conselhos que não sejam indicar ao usuário buscar ajuda profissional!
|
||||
|
||||
Se isso ocorrer no nosso servidor de chat: crie um canal privado para o usuário e o time de moderadores. Isso pode ser feito com o comando `private` do bot.
|
||||
Se isso ocorrer no nosso servidor de chat: crie um canal privado para o usuário e o time de moderadores. Isso pode ser feito com o comando`private` do bot.
|
||||
|
||||
- O usuário tem a privacidade garantida.
|
||||
- O chat público não será mais perturbado.
|
||||
- Outros membros do time podem contribuir caso você se sinta desconfortável ao lidar com a situação sozinho.
|
||||
|
||||
URLs úteis:
|
||||
Links úteis:
|
||||
|
||||
http://suicide.org/international-suicide-hotlines.html
|
||||
|
||||
@@ -386,7 +376,7 @@ Hey @username
|
||||
|
||||
We would love to be able to merge your changes but it looks like there is an error with the CI build. ⚠️
|
||||
|
||||
Assim que você resolver essas issues, nós poderemos rever seu PR e fazer o merge. 😊
|
||||
Once you resolve these issues, we will be able to review your PR and merge it. 😊
|
||||
|
||||
---
|
||||
|
||||
@@ -414,18 +404,18 @@ git fetch upstream
|
||||
git pull upstream main
|
||||
````
|
||||
|
||||
Se você estiver usando uma GUI, basta clicar em `Add a new remote...` e usar o link `git://github.com/freeCodeCamp/freeCodeCamp.git` de cima.
|
||||
If you're using a GUI, you can simply `Add a new remote...` and use the link `git://github.com/freeCodeCamp/freeCodeCamp.git` from above.
|
||||
|
||||
Após sincronizar seu fork e passar no build, poderemos revisar seu PR e fazer o merge. 😊
|
||||
Once you sync your fork and pass the build, we will be able to review your PR and merge it. 😊
|
||||
|
||||
---
|
||||
|
||||
Fique à vontade para recorrer ao artigo [Syncing a Fork](https://help.github.com/articles/syncing-a-fork/) no GitHub para mais ideias de como manter seu fork atualizado com o repositório upstream. 🔄
|
||||
Feel free to reference the ["Syncing a fork"](https://help.github.com/articles/syncing-a-fork/) article on GitHub for more insight on how to keep your fork up-to-date with the upstream repository. 🔄
|
||||
````
|
||||
|
||||
### Merge Conflicts
|
||||
### Conflitos de merge
|
||||
|
||||
> When PR has merge conflicts that need to be resolved.¹
|
||||
> Quando um PR tem conflitos de merge isso precisa ser resolvido.¹
|
||||
|
||||
```markdown
|
||||
Hey @username
|
||||
@@ -450,7 +440,7 @@ Also, it's good practice on GitHub to write a brief description of your changes
|
||||
```markdown
|
||||
Hey @username
|
||||
|
||||
This PR seems to make similar changes as the existing PR <#number>. Assim, vamos fechar esse por ser uma duplicata.
|
||||
This PR seems to make similar changes as the existing PR <#number>. As such, we are going to close this as a duplicate.
|
||||
|
||||
If you feel you have additional changes to expand upon this PR, please feel free to push your commits and request this PR be reopened.
|
||||
|
||||
@@ -488,21 +478,40 @@ If you think we're wrong in closing this issue, please request for it to be reop
|
||||
### Adicionando comentário sobre erros de iniciante
|
||||
|
||||
```markdown
|
||||
Como um novo colaborador, encorajamos você a ler nossas [diretrizes de contribuição](https://contribute.freecodecamp.org).
|
||||
Hi there,
|
||||
|
||||
Esperamos que nossos colaboradores estejam cientes do processo específico deste projeto. Seguindo as orientações religiosamente, você ganha o respeito de outros mantenedores e poupa tempo a todos.
|
||||
Thanks for creating this pull request.
|
||||
|
||||
Alguns exemplos disso são:
|
||||
Please ensure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. Respect the requirements to earn the respect of your fellow maintainers. You will also save everyone time :)
|
||||
|
||||
1. Não edite arquivos diretamente no GitHub – apesar de você poder, não é uma boa ideia.
|
||||
2. Certifique-se de seguir a lista de verificação de PRs e não apenas saia marcando 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. Mantenha as menções e pedidos de revisão no mínimo. Compreendemos que você está entusiasmado em contribuir, e os nossos mantenedores retornarão você assim que tiverem uma chance.
|
||||
5. Não trabalhe diretamente no seu branch `main` - crie um novo branch para as alterações em que está trabalhando.
|
||||
Since you are new here, please slow down and read our [contributing guidelines](https://contribute.freecodecamp.org), as we see that you may still need to catch up on a few things.
|
||||
|
||||
Agradecemos por você usar seu tempo para nos ajudar, e esperamos ver mais contribuições de você.
|
||||
<details>
|
||||
<summary>Here are some examples (expand)</summary>
|
||||
|
||||
Boas contribuições.
|
||||
1. Do not edit files directly on GitHub – while you can, it's not a good idea.
|
||||
|
||||
Typos and formatting errors can break the tests.
|
||||
|
||||
2. Use the correct way to link issues.
|
||||
|
||||
Add the issue number only in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like.
|
||||
|
||||
4. Keep mentions and review requests to a minimum.
|
||||
|
||||
We understand you are excited about contributing, and our maintainers will get back to you when they can.
|
||||
|
||||
5. Do not work directly off your `main` branch.
|
||||
|
||||
You can always create a new branch for the changes you are working on. That way, you can sync change to your PR branch as the main repository moves ahead while your PR is waiting in the merge queue.
|
||||
|
||||
</details>
|
||||
|
||||
Don't worry. You don't have to close this PR. Feel free to ask specific queries on improving your PR here; someone will guide you.
|
||||
|
||||
We are happy you are excited to contribute and appreciate you taking the time to help us. Looking forward to more contributions!
|
||||
|
||||
Happy Contributing.
|
||||
```
|
||||
|
||||
### Fechando issues inválidas
|
||||
@@ -564,9 +573,9 @@ Happy contributing.
|
||||
### Solicitações de atribuição
|
||||
|
||||
```md
|
||||
Normalmente, não atribuímos issues. Em vez disso, aceitamos o primeiro pull request que resolve o problema como um todo.
|
||||
We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue.
|
||||
|
||||
Issues rotuladas com `help wanted` ou `first timers only` estão abertas para contribuições.
|
||||
Issues labelled with `help wanted` or `first timers only` are open for contributions.
|
||||
|
||||
Certifique-se de ler [nossas diretrizes para contribuição](https://contribute.freecodecamp.org/#/). Priorizamos os colaboradores de acordo com as instruções em nosso guia. Faça parte de [nossa sala de bate-papo](https://discord.gg/PRyKn3Vbay) ou [do fórum](https://forum.freecodecamp.org/c/contributors/3) caso precise de ajuda com suas contribuições. Nossos moderadores orientarão você pelo processo.
|
||||
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.
|
||||
```
|
||||
|
||||
@@ -148,7 +148,41 @@ export default connect(null, mapDispatchToProps)(MyComponent);
|
||||
<!-- ### Redux Types File -->
|
||||
<!-- The types associated with the Redux store state are located in `client/src/redux/types.ts`... -->
|
||||
|
||||
## Додаткова література
|
||||
## API
|
||||
|
||||
### Testing
|
||||
|
||||
The `api/` tests are split into two parts:
|
||||
|
||||
1. Unit tests
|
||||
2. Integration tests
|
||||
|
||||
#### Unit Tests
|
||||
|
||||
Unit tests isolate a single function or component. The tests do not need mocking, but will require fixtures.
|
||||
|
||||
The unit tests are located in a new file adjacent the file exporting that being tested:
|
||||
|
||||
```text
|
||||
api/
|
||||
├── src/
|
||||
│ ├── utils.ts
|
||||
│ ├── utils.test.ts
|
||||
```
|
||||
|
||||
#### Integration Tests
|
||||
|
||||
Integration tests test the API as a whole. The tests will require mocking, and should not require fixtures beyond the database seeding data, and a method to authenticate.
|
||||
|
||||
Typically, each integration test file will be directly related to a route. The integration tests are located in the `api/tests/` directory:
|
||||
|
||||
```text
|
||||
api/
|
||||
├── tests/
|
||||
│ ├── settings.ts
|
||||
```
|
||||
|
||||
## Further Literature
|
||||
|
||||
- [Документація TypeScript](https://www.typescriptlang.org/docs/)
|
||||
- [Шпаргалка для TypeScript із React](https://github.com/typescript-cheatsheets/react#readme)
|
||||
|
||||
@@ -305,59 +305,49 @@ Moderating the forum is possible via a cell phone but you may encounter some usa
|
||||
>
|
||||
> Це необхідно для того, щоб ми могли надати вам дозвіл робити записи у наших репозиторіях.
|
||||
|
||||
## Як ми звільняємо неактивних модераторів
|
||||
## How Our Contributors Room Works
|
||||
|
||||
Зверніть увагу, що ми часто видаляємо модераторів, яких вважаємо неактивними. Коли ми так робимо, то надсилаємо наступне повідомлення:
|
||||
Anyone is welcome in the [contributors room on our chat server](https://discord.gg/PRyKn3Vbay). It is the designated chat room for moderators and other campers who contribute to our community in any number of ways, including through study groups.
|
||||
|
||||
```markdown
|
||||
This is a standard message notifying you that, since you don't seem to have been an active moderator recently, we're removing you from our moderator team. We deeply appreciate your help in the past.
|
||||
We assume contributors will read anything in this room that directly mentions them with an **@username**. Everything else is optional, but feel free to read anything anyone posts in there and interact.
|
||||
|
||||
If you think we did this in error, or once you're ready to come back and contribute more, just reply to this message letting us know.
|
||||
```
|
||||
## Dealing with Solicitors
|
||||
|
||||
## Як працює кімната помічників
|
||||
You may be approached by organizations who want to partner or co-brand with freeCodeCamp somehow. Once you realize that this is what they're after, **please stop talking to them** and tell them to email `team[at]freecodecamp.org`.
|
||||
|
||||
Ми вітаємо кожного у [кімнаті помічників на нашому чат-сервері](https://discord.gg/PRyKn3Vbay). Ми створили її для модераторів та інших кемперів, які роблять внесок до нашої спільноти будь-яким чином, включно з навчальними групами.
|
||||
We get proposals like this all the time, and the staff are in the best position to judge whether such a relationship will be worth it for our community (and it rarely is).
|
||||
|
||||
Ми прискаємо, що помічники читають всі повідомлення, у яких вони згадуються через **@username**. Все інше за бажанням, однак не соромтесь читати інші дописи та взаємодіяти з ними.
|
||||
## Dealing with (Mental) Health Inquiries
|
||||
|
||||
## Комунікація із посередниками
|
||||
You may come across situations where users seek medical advice or are dealing with mental health issues and are looking for support.
|
||||
|
||||
До вас можуть звернутися організації, які хочуть стати партнерами або співвласниками бренду freeCodeCamp. Як тільки ви зрозумієте їхні наміри, **закінчуйте діалог** та направте їх на пошту `team[at]freecodecamp.org`.
|
||||
As a matter of policy, you should avoid talking privately about these matters. Should the situation reflect back to freeCodeCamp, we want to have the conversation(s) on record. Make it clear that we are not medical professionals and that you encourage the user to find professional help.
|
||||
|
||||
Нам часто надходять такі пропозиції, тому вигоду співпраці для нашої спільноти краще вирішувати персоналу (зазвичай воно того не варте).
|
||||
As difficult as it sometimes can be, avoid giving any tips or advice and rather point the user in the direction of seeking professional help!
|
||||
|
||||
## Як діяти при зверненнях щодо (психічного) здоров'я
|
||||
|
||||
Іноді трапляються ситуації, коли користувачам потрібна медична допомога, або у них наявні ментальні порушення та вони шукають підтримки.
|
||||
|
||||
Згідно з нашою політикою вам варто уникати приватних розмов щодо таких речей. Якщо ситуація напряму стосується freeCodeCamp, потрібно мати запис розмови. Дайте зрозуміти, що ми не медичні працівники та заохотьте користувача звернутись по медичну допомогу.
|
||||
|
||||
Попри те, що іноді це важко, уникайте підказок чи порад, а радше направте користувача на пошук професійної допомоги!
|
||||
|
||||
Якщо таке трапилося у чаті, створіть приватний канал для користувача та команди модераторів. Це можна зробити за допомогою команди `private`.
|
||||
If this happens on our chat server: Create a private channel for the user and the moderator team. This can be done with the bot's `private` command.
|
||||
|
||||
- Користувачу гарантована конфіденційність.
|
||||
- У публічному чаті більше немає порушень.
|
||||
- Інші учасники команди можуть втрутитися, якщо вам некомфортно справлятися із ситуацією самостійно.
|
||||
|
||||
Корисні посилання:
|
||||
Helpful URLs:
|
||||
|
||||
http://suicide.org/international-suicide-hotlines.html
|
||||
|
||||
## Примітка щодо свободи слова
|
||||
## A Note on Free Speech
|
||||
|
||||
Інколи люди захищатимуть щось образливе або провокативне, обґрунтовуючи це «свободою слова».
|
||||
Sometimes people will defend something offensive or incendiary that they said as "free speech."
|
||||
|
||||
Цей вебкомікс від XKCD ідеально підсумовує думки більшості спільнот стосовно свободи слова.
|
||||
This XKCD comic summarizes perfectly most communities' thoughts on free speech.
|
||||
|
||||
<div align="center"><img src='./images/github/xkcd-free-speech.png' width="400" height="400" /></div>
|
||||
|
||||
Дякуємо за увагу та допомогу спільноті розробників!
|
||||
Thanks for reading this, and thanks for helping the developer community!
|
||||
|
||||
## Зразки відповідей
|
||||
## Reply Templates
|
||||
|
||||
Це зразки відповідей, які можна використовувати під час розгляду запитів на злиття та їх сортування.
|
||||
These are some of the standard reply templates that you may use while reviewing pull requests and triaging issues/pull requests.
|
||||
|
||||
> Ви можете створити власний список збережених відповідей за допомогою вбудованої функції [збережені відповіді](https://github.com/settings/replies/) на GitHub або використовувати подані нижче.
|
||||
|
||||
@@ -414,7 +404,7 @@ git fetch upstream
|
||||
git pull upstream main
|
||||
````
|
||||
|
||||
Якщо ви використовуєте графічний інтерфейс користувача, просто виконайте команду `Add a new remote...` та використайте посилання `git://github.com/freeCodeCamp/freeCodeCamp.git`.
|
||||
If you're using a GUI, you can simply `Add a new remote...` and use the link `git://github.com/freeCodeCamp/freeCodeCamp.git` from above.
|
||||
|
||||
Once you sync your fork and pass the build, we will be able to review your PR and merge it. 😊
|
||||
|
||||
@@ -441,7 +431,7 @@ If you're not familiar with the merge conflict process, feel free to look over G
|
||||
Also, it's good practice on GitHub to write a brief description of your changes when creating a PR. 📝
|
||||
````
|
||||
|
||||
¹ Якщо у новачка виникає конфлікт злиття, то спеціалісти розв’яжуть цю проблему замість нього.
|
||||
¹ If a first-time-contributor has a merge conflict, maintainers will resolve the conflict for them.
|
||||
|
||||
### Дублікат
|
||||
|
||||
@@ -488,19 +478,38 @@ If you think we're wrong in closing this issue, please request for it to be reop
|
||||
### Adding Comment About Newbie Mistakes
|
||||
|
||||
```markdown
|
||||
As a new contributor, we encourage you to read our [contributing guidelines](https://contribute.freecodecamp.org).
|
||||
Hi there,
|
||||
|
||||
We expect our contributors to be aware of the process specific to this project. Following the guidelines religiously earns you the respect of fellow maintainers and saves everyone time.
|
||||
Thanks for creating this pull request.
|
||||
|
||||
Some examples of this are:
|
||||
Please ensure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. Respect the requirements to earn the respect of your fellow maintainers. You will also save everyone time :)
|
||||
|
||||
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. Keep mentions and review requests to a minimum. We understand you are excited about contributing, and our maintainers will get back to you as soon as they get a chance.
|
||||
5. Do not work directly off your `main` branch - create a new branch for the changes you are working on.
|
||||
Since you are new here, please slow down and read our [contributing guidelines](https://contribute.freecodecamp.org), as we see that you may still need to catch up on a few things.
|
||||
|
||||
We appreciate you taking the time to help us, and we hope to see more contributions from you.
|
||||
<details>
|
||||
<summary>Here are some examples (expand)</summary>
|
||||
|
||||
1. Do not edit files directly on GitHub – while you can, it's not a good idea.
|
||||
|
||||
Typos and formatting errors can break the tests.
|
||||
|
||||
2. Use the correct way to link issues.
|
||||
|
||||
Add the issue number only in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like.
|
||||
|
||||
4. Keep mentions and review requests to a minimum.
|
||||
|
||||
We understand you are excited about contributing, and our maintainers will get back to you when they can.
|
||||
|
||||
5. Do not work directly off your `main` branch.
|
||||
|
||||
You can always create a new branch for the changes you are working on. That way, you can sync change to your PR branch as the main repository moves ahead while your PR is waiting in the merge queue.
|
||||
|
||||
</details>
|
||||
|
||||
Don't worry. You don't have to close this PR. Feel free to ask specific queries on improving your PR here; someone will guide you.
|
||||
|
||||
We are happy you are excited to contribute and appreciate you taking the time to help us. Looking forward to more contributions!
|
||||
|
||||
Happy Contributing.
|
||||
```
|
||||
|
||||
Reference in New Issue
Block a user