blocks|key|335809|text|确保您的本地存储库中有所有重要的分支和标记，删除github存储库，通过常规方法重新创建存储库(不使用forking)，并使用git+push+--all推送本地存储库。请注意，如果您有不想发布的本地分支，则可能值得为该操作创建一个临时的干净本地克隆。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|335810|然而，这也将摆脱维基和问题。由于wiki实际上是它自己的存储库，因此可以通过克隆它，然后重新创建和推送来进行类似的处理。回购地址在维基的Git访问页面(git@github.com:user/repo.wiki.git)上。|335811|这就留下了问题。它们可以通过API导出，但据我所知，你只能和你的人一起创建问题和评论，所以不可能完美地导入它们。|335812|因此，如果你需要保留问题，你应该像Thomas+Moulard建议的那样通过github支持。|335813|entityMap|0|LINK|mutability|MUTABLE|url|http://developer.github.com/v3/issues/^0|1R|E|0|24|X|0|E|3|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|Z|8|@]|D|@$9|10|A|11|1|12]]|E|$]]|$1|J|3|K|5|6|7|13|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|14|8|@]|D|@]|E|$]]]|M|$N|$5|O|P|Q|E|$R|S]]]]

Make sure you have all the important branches and tags on your local repo, delete the github repo, recreate the repository through usual means (no forking) and push the local repository back with <code>git push --all</code>. Note that if you have local branches that you don't want to publish, might be worth to create a temporary clean local clone for the operation.

However, this will also get rid of wiki and issues. As the wiki is in fact it's own repository, it can be handled similarly by cloning it and then recreating and pushing. The repo address is on wiki's Git Access page (<code>git@github.com:user/repo.wiki.git</code>).

This leaves issues. They can be exported through the <a href="http://developer.github.com/v3/issues/">API</a>, but as far as I know, you can only create issues and comments with your person, so importing them perfectly is impossible.

So, if you need issues to be preserved, you should go through github support as Thomas Moulard suggests.

blocks|key|335866|text|我得到了类似的问题，并最终使用这个github+help+page来解决它。我不介意wiki和问题跟踪器，因为它是为我的博客使用了另一个用户友好地开发的主题。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|335867|要分离派生的repo，并在多次提交后将其用作自己的存储库，而不会丢失整个历史记录：|335868|git+clone+--bare++git@github.com:user/forked_repo.git|style|CODE|335869|在github网站上创建一个新的空存储库new-repository。并推送镜像版本：|335870|cd+user.github.com.git/|335871|git+push+--mirror+git@github.com:user/new-repository.git|335872|用户可以在github上重命名forked_repository，用另一个名称保存它作为备份，并在需要时检查更新。或者干脆把它删除。|335873|将new-repository重命名为原始名称即可完成此工作。作为一个副作用，你的提交现在出现在你的历史记录中。|335874|entityMap|0|LINK|mutability|MUTABLE|url|https://help.github.com/articles/duplicating-a-repository/^0|H|G|0|0|0|0|1H|0|K|E|0|0|N|0|0|1K|0|F|H|0|1|E|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@$A|12|B|13|1|14]]|C|$]]|$1|D|3|E|5|6|7|15|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|16|8|@$A|17|B|18|H|I]]|9|@]|C|$]]|$1|J|3|K|5|6|7|19|8|@$A|1A|B|1B|H|I]]|9|@]|C|$]]|$1|L|3|M|5|6|7|1C|8|@$A|1D|B|1E|H|I]]|9|@]|C|$]]|$1|N|3|O|5|6|7|1F|8|@$A|1G|B|1H|H|I]]|9|@]|C|$]]|$1|P|3|Q|5|6|7|1I|8|@$A|1J|B|1K|H|I]]|9|@]|C|$]]|$1|R|3|S|5|6|7|1L|8|@$A|1M|B|1N|H|I]]|9|@]|C|$]]|$1|T|3|-4|5|6|7|1O|8|@]|9|@]|C|$]]]|U|$V|$5|W|X|Y|C|$Z|10]]]]

I got the similar problem, and ended up using this <a href="https://help.github.com/articles/duplicating-a-repository/" rel="noreferrer" title="github help">github help page</a> to solve it. I didn't mind about the wiki and issues tracker as it was for my blog using a theme kindly developed by another user.

To detach a forked repo and use it as your own after several commits without losing the whole history:

<code>git clone --bare git@github.com:user/forked_repo.git</code>

Create a new empty reposity <code>new-repository</code> on the github website.
And push a mirrored version:

<code>cd user.github.com.git/</code>

<code>git push --mirror git@github.com:user/new-repository.git</code>

One can rename on github, the <code>forked_repository</code> with another name to keep it as backup and check updates if needed. Or simply delete it.

Renaming the <code>new-repository</code> to the original name does the job. As a side effect, your commits now appear in your history.

How can I make GitHub forget or disassociate that my repo was originally a fork of another project?

I forked a project in GitHub. I can now see "forked from whatever/whatever". The parent repository "whatever/whatever" is no longer maintained. I have been allowed to continue use of the code base of the original repository to create an independent repository.

Is there a way to detach my project from the original repository?

Delete fork dependency of a GitHub repository

GitHub

如何让GitHub忘记或解除我的存储库最初是另一个项目的分支的关联？我在GitHub中创建了一个项目。我现在可以看到"forked from whatever/whatever“。不再维护父存储库"whatever/whatever“。我已经被允许继续使用原始存储库的代码库来创建独立的存储库。有没有办法将我的项目从原始...

问删除GitHub存储库的派生依赖关系
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问删除GitHub存储库的派生依赖关系EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问删除GitHub存储库的派生依赖关系
EN