1/ Yes, that seems the safest approach, as any modification you end up back-porting in nicstrong/projectA will be in a project with the same structure as original-author/projectA. That means pull requests will be easier to organize, since you will be in a project mirroring the original author's project.
2/ If you have massive refactoring going on in nicstrong/projectA-android, I would make a backport branch, carefully merge or cherry-pick what you need from the numerous changes to the backport branch, and then push that branch to nicstrong/projectA. (which means you have added nicstrong/projectA as a remote of nicstrong/projectA-android)
The name of a git repository is heavily dependent on the name of the remote. Go ahead and clone it, then just add a new remote (by a different name) and begin pushing there. At that point, of course, you can go ahead and change the name of the project directory without issue.
发布评论
评论（2）
2011：
1/是的，这似乎是最安全的方法，因为您最终在
nicstrong/projectA中向后移植的任何修改都将位于与original-author/projectA 结构相同的项目中。这意味着拉取请求将更容易组织，因为您将处于镜像原始作者项目的项目中。
2/ 如果您在
nicstrong/projectA-android中进行大规模重构，我会创建一个backport分支，仔细合并或从众多更改中挑选您需要的内容到backport分支，然后将该分支推送到nicstrong/projectA。（这意味着您已将
nicstrong/projectA添加为nicstrong/projectA-android的遥控器）2022：请注意，您可以 直接使用不同的名称创建一个分叉。
2011:
1/ Yes, that seems the safest approach, as any modification you end up back-porting in
nicstrong/projectAwill be in a project with the same structure asoriginal-author/projectA.That means pull requests will be easier to organize, since you will be in a project mirroring the original author's project.
2/ If you have massive refactoring going on in
nicstrong/projectA-android, I would make abackportbranch, carefully merge or cherry-pick what you need from the numerous changes to thebackportbranch, and then push that branch tonicstrong/projectA.(which means you have added
nicstrong/projectAas a remote ofnicstrong/projectA-android)2022: Note that you can create a fork directly with a different name.
git 存储库的名称在很大程度上取决于远程存储库的名称。继续克隆它，然后添加一个新的遥控器（使用不同的名称）并开始推送到那里。当然，此时您可以继续更改项目目录的名称，不会出现任何问题。
The name of a git repository is heavily dependent on the name of the remote. Go ahead and clone it, then just add a new remote (by a different name) and begin pushing there. At that point, of course, you can go ahead and change the name of the project directory without issue.