search

hust-open-atom-club / hust-mirrors

华中科技大学开源镜像站前端
https://mirrors.hust.edu.cn
MIT License
67 stars 21 forks source link

Add:archlinuxcn.md #104

Closed CAICAIIs closed 3 weeks ago

CAICAIIs commented 4 weeks ago

Translate document from Chinese to English and move to 'i18n\en\docusaurus-plugin-content-docs' folder

tttturtle-russ commented 4 weeks ago

Content is good now. We just need to fix the compilation error.

mudongliang commented 3 weeks ago

@CAICAIIs Please use the formatted git commit message. @tttturtle-russ When you merge this PR, please use Square Merge

CAICAIIs commented 3 weeks ago

@CAICAIIs Please use the formatted git commit message. @tttturtle-russ When you merge this PR, please use Square Merge

Thank you for the guidance. I am a beginner in this area and I am currently learning how to use it

mudongliang commented 3 weeks ago
截屏2024-11-03 11 13 55

It's fine. For us, we can merge it as one commit. However, it's good for your future if you can write good git title and commit message.

CAICAIIs commented 3 weeks ago
截屏2024-11-03 11 13 55

It's fine. For us, we can merge it as one commit. However, it's good for your future if you can write good git title and commit message.

You're right, I'm still unfamiliar with the operation. Thank you for pointing it out.

CAICAIIs commented 3 weeks ago
截屏2024-11-03 11 13 55

It's fine. For us, we can merge it as one commit. However, it's good for your future if you can write good git title and commit message.

Can you check again? Thank you for your careful guidance.

mudongliang commented 3 weeks ago

You can check it yourself. The commits in this PR is kind of messy.

mudongliang commented 3 weeks ago

For the commit history, you can check and refer to #102 #103

CAICAIIs commented 3 weeks ago

For the commit history, you can check and refer to #102 #103

Thank you, I am not yet able to handle my commit and am currently studying.

mudongliang commented 3 weeks ago

For the commit history, you can check and refer to #102 #103

Thank you, I am not yet able to handle my commit and am currently studying.

No worry, keep learning. There is always a working method - keep your translation, create a new branch, copy the translation and create a new PR :)

tttturtle-russ commented 3 weeks ago

For the commit history, you can check and refer to #102 #103

Thank you, I am not yet able to handle my commit and am currently studying.

No worry, keep learning. There is always a working method - keep your translation, create a new branch, copy the translation and create a new PR :)

agree, the easiest way is to open a new pr. and you can check how the compilation bug occurred before opening the new pr.

mudongliang commented 3 weeks ago

duplicate with #105