mirror of
https://github.com/freeCodeCamp/freeCodeCamp.git
synced 2026-05-28 18:26:54 +00:00
chore(i18n,docs): processed translations (#49558)
This commit is contained in:
camperbot
@@ -12,43 +12,43 @@ Yes - You can contribute to any of the 30+ languages we have enabled on our tran
|
||||
|
||||
We have user-contributed translations live in some languages. We intend to localize freeCodeCamp into several major world languages. You can read all about this in our [announcement here](https://www.freecodecamp.org/news/help-translate-freecodecamp-language/).
|
||||
|
||||
If you are interested in contributing to translations please make sure you [read this guide](how-to-translate-files.md) first.
|
||||
如果你對參與翻譯貢獻有興趣，請務必首先[閱讀本指南](how-to-translate-files.md)。
|
||||
|
||||
### Can I contribute articles to freeCodeCamp News or videos to freeCodeCamp's YouTube channel?
|
||||
|
||||
Yes - you can contribute to our publication blog and YouTube channel.
|
||||
|
||||
If you're interested in writing articles for freeCodeCamp News, please visit this [publication guide](https://www.freecodecamp.org/news/how-to-write-for-freecodecamp/). In addition, please read our [style guide](https://www.freecodecamp.org/news/developer-news-style-guide/) as this will help you write stronger and more effective articles.
|
||||
如果你有興趣爲 freeCodeCamp News 撰寫文章，請訪問此 [專欄寫作指南](https://www.freecodecamp.org/chinese/news/developer-news-style-guide/)。 In addition, please read our [style guide](https://www.freecodecamp.org/news/developer-news-style-guide/) as this will help you write stronger and more effective articles.
|
||||
|
||||
To help us make educational videos for our YouTube channel, you can follow the [YouTube channel guide here](https://www.freecodecamp.org/news/how-to-contribute-to-the-freecodecamp-community-youtube-channel-b86bce4c865/).
|
||||
|
||||
### How can I report a new bug?
|
||||
### 我如何報告一個新的 bug？
|
||||
|
||||
If you think you've found a bug, first read the ["How to Report a Bug"](https://www.freecodecamp.org/news/how-to-report-a-bug-to-freecodecamp/) article and follow its instructions.
|
||||
|
||||
If you're confident it's a new bug, go ahead and create a new GitHub issue. Be sure to include as much information as possible so that we can reproduce the bug. We have a pre-defined issue template to help you through this.
|
||||
如果你確信這是一個新的bug，請創建一個新的 GitHub issue。 請務必包含儘可能多的信息，以便我們能夠重現 bug。 我們有預設的 issue 模版來幫助你提交 GitHub issue。
|
||||
|
||||
Please note that these GitHub issues are for codebase-related issues and discussions – not for getting help with learning to code. Whenever in doubt, you should [seek assistance on the forum](https://forum.freecodecamp.org) before creating a GitHub issue.
|
||||
請注意，這些 GitHub issues 僅爲了代碼庫相關的問題和討論，而不是爲了獲得編程學習方面的幫助。 當你有疑問時，應該在創建一個 GitHub issue 前[在論壇上尋求幫助](https://forum.freecodecamp.org)。
|
||||
|
||||
### How can I report a security issue?
|
||||
### 我如何報告一個安全問題？
|
||||
|
||||
Please don't create GitHub issues for security issues. Instead, please [follow our security policy](https://contribute.freecodecamp.org/#/security).
|
||||
請不要爲安全問題來創建 GitHub issue。 反之，請 [遵循我們的安全政策](https://contribute.freecodecamp.org/#/security)。
|
||||
|
||||
### I am a student. Can I work on a feature for academic credits?
|
||||
### 我是一名學生。 我可以爲學術學分參與一個功能開發嗎？
|
||||
|
||||
Yes. Please note we are unable to commit to any timelines or paperwork that may be a requirement by your college or university. We receive many pull-requests and code contributions from volunteer developers, and we respect their time and efforts. Out of respect for all of our other contributors, we will not give any PR special priority just because it happens to be school-related.
|
||||
可以的。 請注意，我們無法承諾你的學院或大學可能要求的任何時間表或文書工作。 我們收到了許多來自於志願開發者的推送請求以及代碼貢獻，並且我們尊重他們的時間與勞動。 出於對我們所有其他貢獻者的尊重，我們不會僅僅因爲與學校有關而給予任何優先考慮。
|
||||
|
||||
We request you to plan ahead and work on code contributions with this in mind.
|
||||
我們請求你提前計劃，並在貢獻代碼時知曉這一點。
|
||||
|
||||
### What do these different labels that are tagged on issues mean?
|
||||
### 這些不同的在問題上標籤意味着什麼？
|
||||
|
||||
The code maintainers [triage](https://en.wikipedia.org/wiki/Software_bug#Bug_management) issues and pull requests based on their priority, severity, and other factors. You can [find a complete glossary of their meanings here](https://github.com/freecodecamp/freecodecamp/labels).
|
||||
代碼維護人員會根據優先級、嚴重程度和其他因素對 issue 和 pull request 進行[分類](https://en.wikipedia.org/wiki/Software_bug#Bug_management)。 你可以在這裏找到[其含義的完整詞彙表](https://github.com/freecodecamp/freecodecamp/labels).
|
||||
|
||||
### Where do I start if I want to work on an issue?
|
||||
### 如果我想就一個問題開展工作，我將從哪裏開始？
|
||||
|
||||
You should go through [**`help wanted`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) or [**`first timers only`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22first+timers+only%22) issues for a quick overview of what is available for you to work on.
|
||||
你應該瀏覽標註有 [**`help wanted`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) 或 [**`first timers only`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22first+timers+only%22) 的 issue，以快速瞭解可供你貢獻的內容。
|
||||
|
||||
> [!TIP] **`help wanted`** issues are up for grabs, and you do not need to seek permission before working on them. However, issues with the **`first timers only`** label are special issues that are designed for people who have not contributed to the freeCodeCamp codebase before.
|
||||
> [!TIP] **`help wanted`** issues are up for grabs, and you do not need to seek permission before working on them. 然而，具有 **`first timers only`** 標籤的 issue 是特別爲以前沒有爲 freeCodeCodeCamp 代碼庫貢獻的人設計的任務。
|
||||
|
||||
### I found a typo. Should I report an issue before I can make a pull request?
|
||||
|
||||
@@ -63,8 +63,8 @@ We typically do not assign issues to anyone other than long-time contributors. I
|
||||
1. We are most likely to merge the first pull request that addresses the issue.
|
||||
2. In the case of multiple contributors opening a pull request for the same issue at around the same time, we will give priority to the pull request that best addresses the issue. Some of the things we consider:
|
||||
- Did you include tests?
|
||||
- Did you catch all use cases?
|
||||
- Did you ensure all tests pass, and confirm everything works locally?
|
||||
- 你是否考慮了所有用例？
|
||||
- 你是否確保通過所有測試，並確認所有東西在本地正常運行？
|
||||
3. Finally, we give priority to pull requests which follow our recommended guidelines.
|
||||
- Did you follow the pull request checklist?
|
||||
- Did you give your pull request a meaningful title?
|
||||
@@ -81,7 +81,7 @@ Here are some recommended paths for some of our platforms:
|
||||
- To be a **Forum** moderator, similar to a chat moderator, have an active presence and engage with other forum posters, supporting others in their learning journey, and even giving feedback when asked. Take a look at [The Subforum Leader Handbook](https://forum.freecodecamp.org/t/the-subforum-leader-handbook/326326) for more information.
|
||||
- To be a **GitHub** moderator, help process GitHub issues that are brought up to see if they are valid and (ideally) try to propose solutions for these issues to be picked up by others (or yourself).
|
||||
|
||||
Altogether, be respectful to others. We are humans from all around the world. With that in mind, please also consider using encouraging or supportive language and be mindful of cross-cultural communication.
|
||||
Altogether, be respectful to others. 我們是來自世界各地的人。 With that in mind, please also consider using encouraging or supportive language and be mindful of cross-cultural communication.
|
||||
|
||||
If you practice the above **consistently for a while** and our fellow moderator members recommend you, a staff member will reach out and onboard you to the moderators' team. Open source work is voluntary work and our time is limited. We acknowledge that this is probably true in your case as well. So we emphasize being **consistent** rather than engaging in the community 24/7.
|
||||
|
||||
@@ -100,6 +100,6 @@ Thanks in advance for being polite and patient. Remember – this community is r
|
||||
|
||||
### Additional Assistance
|
||||
|
||||
If you have queries about the stack, architecture of the codebase, translations, or anything else, feel free to reach out to our staff team [on the forum](https://forum.freecodecamp.org/g/team).
|
||||
如果你對技術棧、代碼庫的架構、翻譯或其他方面有疑問，請隨時[在論壇上](https://forum.freecodecamp.org/g/team)與我們的員工團隊聯繫。
|
||||
|
||||
**You can email our developer staff at: `dev[at]freecodecamp.org`**
|
||||
**你可以發郵件到 `dev[at]freecodecamp.org` 以聯繫我們團隊的開發者。**
|
||||
|
||||
@@ -158,12 +158,12 @@ Once one of the staff members approves a release, the pipeline will push the cha
|
||||
|
||||
Here is the current test, build and deployment status of the codebase.
|
||||
|
||||
| Branch | Unit Tests | Integration Tests | Builds & Deployments |
|
||||
|:-------------------------------------------------------------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |:--------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| [`main`](https://github.com/freeCodeCamp/freeCodeCamp/tree/main) | [](https://github.com/freeCodeCamp/freeCodeCamp/actions?query=workflow%3A%22Node.js+CI%22) | [](https://dashboard.cypress.io/projects/ke77ns/analytics/runs-over-time) | - |
|
||||
| [`prod-staging`](https://github.com/freeCodeCamp/freeCodeCamp/tree/prod-staging) | [](https://github.com/freeCodeCamp/freeCodeCamp/actions?query=workflow%3A%22Node.js+CI%22+branch%3Aprod-staging) | [](https://dashboard.cypress.io/projects/ke77ns/analytics/runs-over-time) | [Azure Pipelines](https://dev.azure.com/freeCodeCamp-org/freeCodeCamp/_dashboards/dashboard/d59f36b9-434a-482d-8dbd-d006b71713d4) |
|
||||
| [`prod-current`](https://github.com/freeCodeCamp/freeCodeCamp/tree/prod-staging) | [](https://github.com/freeCodeCamp/freeCodeCamp/actions?query=workflow%3A%22Node.js+CI%22+branch%3Aprod-current) | [](https://dashboard.cypress.io/projects/ke77ns/analytics/runs-over-time) | [Azure Pipelines](https://dev.azure.com/freeCodeCamp-org/freeCodeCamp/_dashboards/dashboard/d59f36b9-434a-482d-8dbd-d006b71713d4) |
|
||||
| `prod-next` (experimental, upcoming) | - | - | - |
|
||||
| Branch | Unit Tests | Integration Tests | Builds & Deployments |
|
||||
|:-------------------------------------------------------------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| [`main`](https://github.com/freeCodeCamp/freeCodeCamp/tree/main) | [](https://github.com/freeCodeCamp/freeCodeCamp/actions?query=workflow%3A%22Node.js+CI%22) | [](https://dashboard.cypress.io/projects/ke77ns/analytics/runs-over-time) | - |
|
||||
| [`prod-staging`](https://github.com/freeCodeCamp/freeCodeCamp/tree/prod-staging) | [](https://github.com/freeCodeCamp/freeCodeCamp/actions?query=workflow%3A%22Node.js+CI%22+branch%3Aprod-staging) | [](https://dashboard.cypress.io/projects/ke77ns/analytics/runs-over-time) | [Azure Pipelines](https://dev.azure.com/freeCodeCamp-org/freeCodeCamp/_dashboards/dashboard/d59f36b9-434a-482d-8dbd-d006b71713d4) |
|
||||
| [`prod-current`](https://github.com/freeCodeCamp/freeCodeCamp/tree/prod-staging) | [](https://github.com/freeCodeCamp/freeCodeCamp/actions?query=workflow%3A%22Node.js+CI%22+branch%3Aprod-current) | [](https://dashboard.cypress.io/projects/ke77ns/analytics/runs-over-time) | [Azure Pipelines](https://dev.azure.com/freeCodeCamp-org/freeCodeCamp/_dashboards/dashboard/d59f36b9-434a-482d-8dbd-d006b71713d4) |
|
||||
| `prod-next` (experimental, upcoming) | - | - | - |
|
||||
|
||||
## Early access and beta testing
|
||||
|
||||
@@ -873,11 +873,11 @@ You would need a PAT, that you can grab from here: https://dev.azure.com/freeCod
|
||||
|
||||
Navigate to [Azure Devops](https://dev.azure.com/freeCodeCamp-org) and register the agent from scratch in the requisite [deployment groups](https://dev.azure.com/freeCodeCamp-org/freeCodeCamp/_machinegroup).
|
||||
|
||||
> [!NOTE] You should run the scripts in the home directory, and make sure no other `azagent` directory exists.
|
||||
> [!NOTE] 你應該在主目錄運行腳本，並確保沒有其他 `azagent` 目錄存在。
|
||||
|
||||
### Updating agents
|
||||
|
||||
Currently updating agents requires them to be removed and reconfigured. This is required for them to correctly pick up `PATH` values and other system environment variables. We need to do this for instance updating Node.js on our deployment target VMs.
|
||||
Currently updating agents requires them to be removed and reconfigured. This is required for them to correctly pick up `PATH` values and other system environment variables. 例如，我們需要在部署目標虛擬機上更新 Node.js 時這樣做。
|
||||
|
||||
1. Navigate and check status of the service
|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
> **Note:** This is an **optional** step and is required only when working with email workflows
|
||||
> **注意：** 這是一個 **可選的** 步驟，並且僅在處理電子郵件工作流時需要
|
||||
|
||||
- [Introduction](#introduction)
|
||||
- [Installing MailHog](#installing-mailhog)
|
||||
@@ -35,7 +35,7 @@ When the installation completes, you can start [using MailHog](#using-mailhog).
|
||||
|
||||
<details><summary>Installing MailHog on macOS</summary>
|
||||
|
||||
Install MailHog on macOS with [Homebrew](https://brew.sh/):
|
||||
使用 [Homebrew](https://brew.sh/) 在 macOS 上安裝 MailHog：
|
||||
|
||||
```bash
|
||||
brew install mailhog
|
||||
@@ -44,7 +44,7 @@ brew services start mailhog
|
||||
|
||||
The above commands will start a mailhog service in the background.
|
||||
|
||||
When the installation completes, you can start [using MailHog](#using-mailhog).
|
||||
安裝完成後，你可以開始[使用 MailHog](#using-mailhog)。
|
||||
|
||||
</details>
|
||||
|
||||
@@ -52,37 +52,37 @@ When the installation completes, you can start [using MailHog](#using-mailhog).
|
||||
|
||||
Download the latest version of MailHog from [MailHog's official repository](https://github.com/mailhog/MailHog/releases). Locate and click on the link for your Windows version (32 or 64 bit) and a `.exe` file will be downloaded to your computer.
|
||||
|
||||
When the download completes, click to open the file. A Windows firewall notification may appear, requesting access permission for MailHog. A standard Windows command line prompt will open where MailHog will be running once firewall access is granted.
|
||||
下載完成後，單擊以打開文件。 可能會出現 Windows 防火牆通知，爲 MailHog 請求訪問權限。 一旦授予防火牆訪問權限，將打開一個標準的 Windows 命令行提示符，MailHog 將在其中運行。
|
||||
|
||||
Close MailHog by closing the command prompt window. To start MailHog again, click on the MailHog executable (`.exe`) file that was downloaded initially - it is not necessary to download a new MailHog installation file.
|
||||
通過關閉命令提示符窗口來關閉 MailHog。 To start MailHog again, click on the MailHog executable (`.exe`) file that was downloaded initially - it is not necessary to download a new MailHog installation file.
|
||||
|
||||
Start [using MailHog](#using-mailhog).
|
||||
開始[使用 MailHog](#using-mailhog)。
|
||||
|
||||
</details>
|
||||
|
||||
<details><summary>Installing MailHog on Linux</summary>
|
||||
|
||||
First, install [Go](https://golang.org).
|
||||
首先，安裝 [Go](https://golang.org)。
|
||||
|
||||
Run the following commands to install GO on Debian-based systems like Ubuntu and Linux Mint.
|
||||
在基於 Debian 的系統（如 Ubuntu 和 Linux Mint）上，運行以下命令安裝 GO。
|
||||
|
||||
```bash
|
||||
sudo apt-get install golang
|
||||
```
|
||||
|
||||
Run the following commands to install GO on RPM-based systems like CentOS, Fedora, Red Hat Linux, etc.
|
||||
在基於 RPM 的系統（如 CentOS、Fedora、Red Hat Linux 等）上，運行以下命令安裝 GO。
|
||||
|
||||
```bash
|
||||
sudo dnf install golang
|
||||
```
|
||||
|
||||
Alternatively, run the following commands to install GO.
|
||||
或者，運行以下命令來安裝 GO。
|
||||
|
||||
```bash
|
||||
sudo yum install golang
|
||||
```
|
||||
|
||||
Now set the path for Go with the following commands.
|
||||
現在使用以下命令設置 Go 的路徑。
|
||||
|
||||
```bash
|
||||
echo "export GOPATH=$HOME/go" >> ~/.profile
|
||||
@@ -90,7 +90,7 @@ echo 'export PATH=$PATH:/usr/local/go/bin:$GOPATH/bin' >> ~/.profile
|
||||
source ~/.profile
|
||||
```
|
||||
|
||||
Finally, enter the commands below to install and run MailHog.
|
||||
最後，輸入以下命令來安裝和運行 MailHog。
|
||||
|
||||
```bash
|
||||
go get github.com/mailhog/MailHog
|
||||
@@ -98,7 +98,7 @@ sudo cp /home/$(whoami)/go/bin/MailHog /usr/local/bin/mailhog
|
||||
mailhog
|
||||
```
|
||||
|
||||
Start [using MailHog](#using-mailhog).
|
||||
開始[使用 MailHog](#using-mailhog)。
|
||||
|
||||
</details>
|
||||
|
||||
|
||||
@@ -53,7 +53,7 @@ First, visit the `config/i18n.ts` file to add the language to the list of availa
|
||||
|
||||
- `Languages`: Add the new language to `Languages` enum, similar to the others. The string value here will be used in the `.env` file to set a build language later.
|
||||
- `availableLangs`: Add the new property from the `Languages` enum to both the `client` and `curriculum` arrays.
|
||||
- `i18nextCodes`: These are the ISO language codes for each language. You will need to add the appropriate ISO code for the language you are enabling. These do need to be unique for each language.
|
||||
- `i18nextCodes`：這些是每種語言的 ISO 語言代碼。 You will need to add the appropriate ISO code for the language you are enabling. These do need to be unique for each language.
|
||||
- `LangNames`: These are the display names for the language selector in the navigation menu.
|
||||
- `LangCodes`: These are the language codes used for formatting dates and numbers. These should be Unicode CLDR codes instead of ISO codes.
|
||||
- `hiddenLangs`: These languages will not be displayed in the navigation menu. This is used for languages that are not yet ready for release.
|
||||
|
||||
+20
-20
@@ -12,43 +12,43 @@ Yes - You can contribute to any of the 30+ languages we have enabled on our tran
|
||||
|
||||
We have user-contributed translations live in some languages. We intend to localize freeCodeCamp into several major world languages. You can read all about this in our [announcement here](https://www.freecodecamp.org/news/help-translate-freecodecamp-language/).
|
||||
|
||||
If you are interested in contributing to translations please make sure you [read this guide](how-to-translate-files.md) first.
|
||||
如果你对参与翻译贡献有兴趣，请务必首先[阅读本指南](how-to-translate-files.md)。
|
||||
|
||||
### Can I contribute articles to freeCodeCamp News or videos to freeCodeCamp's YouTube channel?
|
||||
|
||||
Yes - you can contribute to our publication blog and YouTube channel.
|
||||
|
||||
If you're interested in writing articles for freeCodeCamp News, please visit this [publication guide](https://www.freecodecamp.org/news/how-to-write-for-freecodecamp/). In addition, please read our [style guide](https://www.freecodecamp.org/news/developer-news-style-guide/) as this will help you write stronger and more effective articles.
|
||||
如果你有兴趣为 freeCodeCamp News 撰写文章，请访问此 [专栏写作指南](https://www.freecodecamp.org/chinese/news/developer-news-style-guide/)。 In addition, please read our [style guide](https://www.freecodecamp.org/news/developer-news-style-guide/) as this will help you write stronger and more effective articles.
|
||||
|
||||
To help us make educational videos for our YouTube channel, you can follow the [YouTube channel guide here](https://www.freecodecamp.org/news/how-to-contribute-to-the-freecodecamp-community-youtube-channel-b86bce4c865/).
|
||||
|
||||
### How can I report a new bug?
|
||||
### 我如何报告一个新的 bug？
|
||||
|
||||
If you think you've found a bug, first read the ["How to Report a Bug"](https://www.freecodecamp.org/news/how-to-report-a-bug-to-freecodecamp/) article and follow its instructions.
|
||||
|
||||
If you're confident it's a new bug, go ahead and create a new GitHub issue. Be sure to include as much information as possible so that we can reproduce the bug. We have a pre-defined issue template to help you through this.
|
||||
如果你确信这是一个新的bug，请创建一个新的 GitHub issue。 请务必包含尽可能多的信息，以便我们能够重现 bug。 我们有预设的 issue 模版来帮助你提交 GitHub issue。
|
||||
|
||||
Please note that these GitHub issues are for codebase-related issues and discussions – not for getting help with learning to code. Whenever in doubt, you should [seek assistance on the forum](https://forum.freecodecamp.org) before creating a GitHub issue.
|
||||
请注意，这些 GitHub issues 仅为了代码库相关的问题和讨论，而不是为了获得编程学习方面的帮助。 当你有疑问时，应该在创建一个 GitHub issue 前[在论坛上寻求帮助](https://forum.freecodecamp.org)。
|
||||
|
||||
### How can I report a security issue?
|
||||
### 我如何报告一个安全问题？
|
||||
|
||||
Please don't create GitHub issues for security issues. Instead, please [follow our security policy](https://contribute.freecodecamp.org/#/security).
|
||||
请不要为安全问题来创建 GitHub issue。 反之，请 [遵循我们的安全政策](https://contribute.freecodecamp.org/#/security)。
|
||||
|
||||
### I am a student. Can I work on a feature for academic credits?
|
||||
### 我是一名学生。 我可以为学术学分参与一个功能开发吗？
|
||||
|
||||
Yes. Please note we are unable to commit to any timelines or paperwork that may be a requirement by your college or university. We receive many pull-requests and code contributions from volunteer developers, and we respect their time and efforts. Out of respect for all of our other contributors, we will not give any PR special priority just because it happens to be school-related.
|
||||
可以的。 请注意，我们无法承诺你的学院或大学可能要求的任何时间表或文书工作。 我们收到了许多来自于志愿开发者的推送请求以及代码贡献，并且我们尊重他们的时间与劳动。 出于对我们所有其他贡献者的尊重，我们不会仅仅因为与学校有关而给予任何优先考虑。
|
||||
|
||||
We request you to plan ahead and work on code contributions with this in mind.
|
||||
我们请求你提前计划，并在贡献代码时知晓这一点。
|
||||
|
||||
### What do these different labels that are tagged on issues mean?
|
||||
### 这些不同的在问题上标签意味着什么？
|
||||
|
||||
The code maintainers [triage](https://en.wikipedia.org/wiki/Software_bug#Bug_management) issues and pull requests based on their priority, severity, and other factors. You can [find a complete glossary of their meanings here](https://github.com/freecodecamp/freecodecamp/labels).
|
||||
代码维护人员会根据优先级、严重程度和其他因素对 issue 和 pull request 进行[分类](https://en.wikipedia.org/wiki/Software_bug#Bug_management)。 你可以在这里找到[其含义的完整词汇表](https://github.com/freecodecamp/freecodecamp/labels).
|
||||
|
||||
### Where do I start if I want to work on an issue?
|
||||
### 如果我想就一个问题开展工作，我将从哪里开始？
|
||||
|
||||
You should go through [**`help wanted`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) or [**`first timers only`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22first+timers+only%22) issues for a quick overview of what is available for you to work on.
|
||||
你应该浏览标注有 [**`help wanted`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) 或 [**`first timers only`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22first+timers+only%22) 的 issue，以快速了解可供你贡献的内容。
|
||||
|
||||
> [!TIP] **`help wanted`** issues are up for grabs, and you do not need to seek permission before working on them. However, issues with the **`first timers only`** label are special issues that are designed for people who have not contributed to the freeCodeCamp codebase before.
|
||||
> [!TIP] **`help wanted`** issues are up for grabs, and you do not need to seek permission before working on them. 然而，具有 **`first timers only`** 标签的 issue 是特别为以前没有为 freeCodeCodeCamp 代码库贡献的人设计的任务。
|
||||
|
||||
### I found a typo. Should I report an issue before I can make a pull request?
|
||||
|
||||
@@ -63,8 +63,8 @@ We typically do not assign issues to anyone other than long-time contributors. I
|
||||
1. We are most likely to merge the first pull request that addresses the issue.
|
||||
2. In the case of multiple contributors opening a pull request for the same issue at around the same time, we will give priority to the pull request that best addresses the issue. Some of the things we consider:
|
||||
- Did you include tests?
|
||||
- Did you catch all use cases?
|
||||
- Did you ensure all tests pass, and confirm everything works locally?
|
||||
- 你是否考虑了所有用例？
|
||||
- 你是否确保通过所有测试，并确认所有东西在本地正常运行？
|
||||
3. Finally, we give priority to pull requests which follow our recommended guidelines.
|
||||
- Did you follow the pull request checklist?
|
||||
- Did you give your pull request a meaningful title?
|
||||
@@ -81,7 +81,7 @@ Here are some recommended paths for some of our platforms:
|
||||
- To be a **Forum** moderator, similar to a chat moderator, have an active presence and engage with other forum posters, supporting others in their learning journey, and even giving feedback when asked. Take a look at [The Subforum Leader Handbook](https://forum.freecodecamp.org/t/the-subforum-leader-handbook/326326) for more information.
|
||||
- To be a **GitHub** moderator, help process GitHub issues that are brought up to see if they are valid and (ideally) try to propose solutions for these issues to be picked up by others (or yourself).
|
||||
|
||||
Altogether, be respectful to others. We are humans from all around the world. With that in mind, please also consider using encouraging or supportive language and be mindful of cross-cultural communication.
|
||||
Altogether, be respectful to others. 我们是来自世界各地的人。 With that in mind, please also consider using encouraging or supportive language and be mindful of cross-cultural communication.
|
||||
|
||||
If you practice the above **consistently for a while** and our fellow moderator members recommend you, a staff member will reach out and onboard you to the moderators' team. Open source work is voluntary work and our time is limited. We acknowledge that this is probably true in your case as well. So we emphasize being **consistent** rather than engaging in the community 24/7.
|
||||
|
||||
@@ -100,6 +100,6 @@ Thanks in advance for being polite and patient. Remember – this community is r
|
||||
|
||||
### Additional Assistance
|
||||
|
||||
If you have queries about the stack, architecture of the codebase, translations, or anything else, feel free to reach out to our staff team [on the forum](https://forum.freecodecamp.org/g/team).
|
||||
如果你对技术栈、代码库的架构、翻译或其他方面有疑问，请随时[在论坛上](https://forum.freecodecamp.org/g/team)与我们的员工团队联系。
|
||||
|
||||
**You can email our developer staff at: `dev[at]freecodecamp.org`**
|
||||
**你可以发邮件到 `dev[at]freecodecamp.org` 以联系我们团队的开发者。**
|
||||
|
||||
@@ -158,12 +158,12 @@ Once one of the staff members approves a release, the pipeline will push the cha
|
||||
|
||||
Here is the current test, build and deployment status of the codebase.
|
||||
|
||||
| Branch | Unit Tests | Integration Tests | Builds & Deployments |
|
||||
|:-------------------------------------------------------------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |:--------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| [`main`](https://github.com/freeCodeCamp/freeCodeCamp/tree/main) | [](https://github.com/freeCodeCamp/freeCodeCamp/actions?query=workflow%3A%22Node.js+CI%22) | [](https://dashboard.cypress.io/projects/ke77ns/analytics/runs-over-time) | - |
|
||||
| [`prod-staging`](https://github.com/freeCodeCamp/freeCodeCamp/tree/prod-staging) | [](https://github.com/freeCodeCamp/freeCodeCamp/actions?query=workflow%3A%22Node.js+CI%22+branch%3Aprod-staging) | [](https://dashboard.cypress.io/projects/ke77ns/analytics/runs-over-time) | [Azure Pipelines](https://dev.azure.com/freeCodeCamp-org/freeCodeCamp/_dashboards/dashboard/d59f36b9-434a-482d-8dbd-d006b71713d4) |
|
||||
| [`prod-current`](https://github.com/freeCodeCamp/freeCodeCamp/tree/prod-staging) | [](https://github.com/freeCodeCamp/freeCodeCamp/actions?query=workflow%3A%22Node.js+CI%22+branch%3Aprod-current) | [](https://dashboard.cypress.io/projects/ke77ns/analytics/runs-over-time) | [Azure Pipelines](https://dev.azure.com/freeCodeCamp-org/freeCodeCamp/_dashboards/dashboard/d59f36b9-434a-482d-8dbd-d006b71713d4) |
|
||||
| `prod-next` (experimental, upcoming) | - | - | - |
|
||||
| Branch | Unit Tests | Integration Tests | Builds & Deployments |
|
||||
|:-------------------------------------------------------------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| [`main`](https://github.com/freeCodeCamp/freeCodeCamp/tree/main) | [](https://github.com/freeCodeCamp/freeCodeCamp/actions?query=workflow%3A%22Node.js+CI%22) | [](https://dashboard.cypress.io/projects/ke77ns/analytics/runs-over-time) | - |
|
||||
| [`prod-staging`](https://github.com/freeCodeCamp/freeCodeCamp/tree/prod-staging) | [](https://github.com/freeCodeCamp/freeCodeCamp/actions?query=workflow%3A%22Node.js+CI%22+branch%3Aprod-staging) | [](https://dashboard.cypress.io/projects/ke77ns/analytics/runs-over-time) | [Azure Pipelines](https://dev.azure.com/freeCodeCamp-org/freeCodeCamp/_dashboards/dashboard/d59f36b9-434a-482d-8dbd-d006b71713d4) |
|
||||
| [`prod-current`](https://github.com/freeCodeCamp/freeCodeCamp/tree/prod-staging) | [](https://github.com/freeCodeCamp/freeCodeCamp/actions?query=workflow%3A%22Node.js+CI%22+branch%3Aprod-current) | [](https://dashboard.cypress.io/projects/ke77ns/analytics/runs-over-time) | [Azure Pipelines](https://dev.azure.com/freeCodeCamp-org/freeCodeCamp/_dashboards/dashboard/d59f36b9-434a-482d-8dbd-d006b71713d4) |
|
||||
| `prod-next` (experimental, upcoming) | - | - | - |
|
||||
|
||||
## Early access and beta testing
|
||||
|
||||
@@ -873,11 +873,11 @@ You would need a PAT, that you can grab from here: https://dev.azure.com/freeCod
|
||||
|
||||
Navigate to [Azure Devops](https://dev.azure.com/freeCodeCamp-org) and register the agent from scratch in the requisite [deployment groups](https://dev.azure.com/freeCodeCamp-org/freeCodeCamp/_machinegroup).
|
||||
|
||||
> [!NOTE] You should run the scripts in the home directory, and make sure no other `azagent` directory exists.
|
||||
> [!NOTE] 你应该在主目录运行脚本，并确保没有其他 `azagent` 目录存在。
|
||||
|
||||
### Updating agents
|
||||
|
||||
Currently updating agents requires them to be removed and reconfigured. This is required for them to correctly pick up `PATH` values and other system environment variables. We need to do this for instance updating Node.js on our deployment target VMs.
|
||||
Currently updating agents requires them to be removed and reconfigured. This is required for them to correctly pick up `PATH` values and other system environment variables. 例如，我们需要在部署目标虚拟机上更新 Node.js 时这样做。
|
||||
|
||||
1. Navigate and check status of the service
|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
> **Note:** This is an **optional** step and is required only when working with email workflows
|
||||
> **注意：** 这是一个 **可选的** 步骤，并且仅在处理电子邮件工作流时需要
|
||||
|
||||
- [Introduction](#introduction)
|
||||
- [Installing MailHog](#installing-mailhog)
|
||||
@@ -35,7 +35,7 @@ When the installation completes, you can start [using MailHog](#using-mailhog).
|
||||
|
||||
<details><summary>Installing MailHog on macOS</summary>
|
||||
|
||||
Install MailHog on macOS with [Homebrew](https://brew.sh/):
|
||||
使用 [Homebrew](https://brew.sh/) 在 macOS 上安装 MailHog：
|
||||
|
||||
```bash
|
||||
brew install mailhog
|
||||
@@ -44,7 +44,7 @@ brew services start mailhog
|
||||
|
||||
The above commands will start a mailhog service in the background.
|
||||
|
||||
When the installation completes, you can start [using MailHog](#using-mailhog).
|
||||
安装完成后，你可以开始[使用 MailHog](#using-mailhog)。
|
||||
|
||||
</details>
|
||||
|
||||
@@ -52,37 +52,37 @@ When the installation completes, you can start [using MailHog](#using-mailhog).
|
||||
|
||||
Download the latest version of MailHog from [MailHog's official repository](https://github.com/mailhog/MailHog/releases). Locate and click on the link for your Windows version (32 or 64 bit) and a `.exe` file will be downloaded to your computer.
|
||||
|
||||
When the download completes, click to open the file. A Windows firewall notification may appear, requesting access permission for MailHog. A standard Windows command line prompt will open where MailHog will be running once firewall access is granted.
|
||||
下载完成后，单击以打开文件。 可能会出现 Windows 防火墙通知，为 MailHog 请求访问权限。 一旦授予防火墙访问权限，将打开一个标准的 Windows 命令行提示符，MailHog 将在其中运行。
|
||||
|
||||
Close MailHog by closing the command prompt window. To start MailHog again, click on the MailHog executable (`.exe`) file that was downloaded initially - it is not necessary to download a new MailHog installation file.
|
||||
通过关闭命令提示符窗口来关闭 MailHog。 To start MailHog again, click on the MailHog executable (`.exe`) file that was downloaded initially - it is not necessary to download a new MailHog installation file.
|
||||
|
||||
Start [using MailHog](#using-mailhog).
|
||||
开始[使用 MailHog](#using-mailhog)。
|
||||
|
||||
</details>
|
||||
|
||||
<details><summary>Installing MailHog on Linux</summary>
|
||||
|
||||
First, install [Go](https://golang.org).
|
||||
首先，安装 [Go](https://golang.org)。
|
||||
|
||||
Run the following commands to install GO on Debian-based systems like Ubuntu and Linux Mint.
|
||||
在基于 Debian 的系统（如 Ubuntu 和 Linux Mint）上，运行以下命令安装 GO。
|
||||
|
||||
```bash
|
||||
sudo apt-get install golang
|
||||
```
|
||||
|
||||
Run the following commands to install GO on RPM-based systems like CentOS, Fedora, Red Hat Linux, etc.
|
||||
在基于 RPM 的系统（如 CentOS、Fedora、Red Hat Linux 等）上，运行以下命令安装 GO。
|
||||
|
||||
```bash
|
||||
sudo dnf install golang
|
||||
```
|
||||
|
||||
Alternatively, run the following commands to install GO.
|
||||
或者，运行以下命令来安装 GO。
|
||||
|
||||
```bash
|
||||
sudo yum install golang
|
||||
```
|
||||
|
||||
Now set the path for Go with the following commands.
|
||||
现在使用以下命令设置 Go 的路径。
|
||||
|
||||
```bash
|
||||
echo "export GOPATH=$HOME/go" >> ~/.profile
|
||||
@@ -90,7 +90,7 @@ echo 'export PATH=$PATH:/usr/local/go/bin:$GOPATH/bin' >> ~/.profile
|
||||
source ~/.profile
|
||||
```
|
||||
|
||||
Finally, enter the commands below to install and run MailHog.
|
||||
最后，输入以下命令来安装和运行 MailHog。
|
||||
|
||||
```bash
|
||||
go get github.com/mailhog/MailHog
|
||||
@@ -98,7 +98,7 @@ sudo cp /home/$(whoami)/go/bin/MailHog /usr/local/bin/mailhog
|
||||
mailhog
|
||||
```
|
||||
|
||||
Start [using MailHog](#using-mailhog).
|
||||
开始[使用 MailHog](#using-mailhog)。
|
||||
|
||||
</details>
|
||||
|
||||
|
||||
@@ -53,7 +53,7 @@ First, visit the `config/i18n.ts` file to add the language to the list of availa
|
||||
|
||||
- `Languages`: Add the new language to `Languages` enum, similar to the others. The string value here will be used in the `.env` file to set a build language later.
|
||||
- `availableLangs`: Add the new property from the `Languages` enum to both the `client` and `curriculum` arrays.
|
||||
- `i18nextCodes`: These are the ISO language codes for each language. You will need to add the appropriate ISO code for the language you are enabling. These do need to be unique for each language.
|
||||
- `i18nextCodes`：这些是每种语言的 ISO 语言代码。 You will need to add the appropriate ISO code for the language you are enabling. These do need to be unique for each language.
|
||||
- `LangNames`: These are the display names for the language selector in the navigation menu.
|
||||
- `LangCodes`: These are the language codes used for formatting dates and numbers. These should be Unicode CLDR codes instead of ISO codes.
|
||||
- `hiddenLangs`: These languages will not be displayed in the navigation menu. This is used for languages that are not yet ready for release.
|
||||
|
||||
Reference in New Issue
Block a user