This repository will be deprecated and archived. The API documentation will be migrated to the engine repository.
Why?
We are fed up with the troubles brought by git submodules:
- Every time we create a branch in the engine repository to develop a feature, we have to carefully handle the git submodule references to prevent referencing old versions when merging branches.
- We host our code on multiple platforms, and git submodules do not support automatically switching repository links based on the code hosting platform.
该仓库将被弃用并归档。API 文档将会迁移到引擎仓库。
为什么?
我们已经受够了 git submodule 带来的麻烦:
- 每次在引擎仓库上创建分支开发功能,都要小心翼翼地处理 git submodule 的引用,防止合并分支时引用到旧版本
- 我们的代码托管在多个平台上,git submodule 并不支持自动根据代码托管平台切换仓库链接
This repository will be deprecated and archived. The API documentation will be migrated to the engine repository.
Why?
We are fed up with the troubles brought by git submodules:
该仓库将被弃用并归档。API 文档将会迁移到引擎仓库。
为什么?
我们已经受够了 git submodule 带来的麻烦: