瀏覽代碼

Merge pull request #7534 from mat128/fix_build_instructions_7533

Docs: Temporary change before getting rid of the custom builds guide. See #6770.
Piotrek Koszuliński 5 年之前
父節點
當前提交
5e123dfdd1
共有 2 個文件被更改,包括 14 次插入7 次删除
  1. 9 2
      docs/builds/guides/development/custom-builds.md
  2. 5 5
      docs/builds/guides/integration/advanced-setup.md

+ 9 - 2
docs/builds/guides/development/custom-builds.md

@@ -38,13 +38,20 @@ In order to start developing CKEditor 5 you will require:
 Start with [forking](https://help.github.com/articles/fork-a-repo/) one of the official builds (it will serve as the starting point for your custom one) and then clone your fork:
 
 ```bash
-git clone -b stable git@github.com:<your-username>/ckeditor5-build-classic.git
+git clone -b stable git@github.com:<your-username>/ckeditor5.git
+```
+
+Builds are available in the `packages/` directory. The directories are named `ckeditor5-build-*`.
+For example, use the following command to get to the classic build:
+
+```bash
+cd packages/ckeditor5-build-classic
 ```
 
 To make updating easier you may optionally add the original build repository to your Git remotes:
 
 ```bash
-git remote add upstream https://github.com/ckeditor/ckeditor5-build-classic.git
+git remote add upstream https://github.com/ckeditor/ckeditor5.git
 ```
 
 <info-box hint>

文件差異過大導致無法顯示
+ 5 - 5
docs/builds/guides/integration/advanced-setup.md