叉重要GitHub回购

本文介绍了叉重要GitHub回购的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述 我们喜欢复制这些文件并将它们粘贴到回购站中。我有一堆我以Gist形式制作的模板，所以人们可以在底部讨论它们。并在那里做一个插件。是否可以通过GitHub网站或客户端将Gist分发给Repo？如果不是这两者中的任何一个，是否可以通过shell来完成？ 是，直接！ 转至 https://github.com/new/import ，并在您的要点和新回购的名称的网址。 我只是放在 https://gist.github.com/RichardBronosky/1aed6606b1283277e7ff9eaa18097e78 和AWS_subnets和它创造 https://github.com/RichardBronosky/AWS_subnets 。 重要功能注释 PRO：保留所有以前的提交历史，包括提交消息 很多人都没有意识到gist提交可能会提交您无法看到的消息他的网络界面。上述要点有2 非常decrsiptive提交邮件我COMMITED在我的本地克隆和推出。它们隐藏在网页界面中，但显示在克隆中，并且使用此导入功能创建了新的回购站。 PRO：它保留要旨从其他作者 提交 CON ：尽管＃2，它只显示1个贡献者（这是我自己）。 CON：即使我要点显示从nboubakr / subnet.py分叉，这个新的/导入的 GitHub库确实 判决 这很好，我非常欣赏PRO。缺点是不足以让我觉得其他方法会更好。 我将在未来广泛使用它，因为我经常创建一个能够回答一些Stack的要点溢出问题。然后我将其扩展并认识到它应该是一个完整的回购。 不是我认为我的作品具有重要意义，而是因为我认为我的提交信息值得分享。这是因为我很懒惰，并且倾向于不想创建重复我已经在提交消息中说过的文档。 I have a bunch of templates I made in Gist form so people can discuss them at the bottom.We like to copy these files and paste them into a repo and make an addon there. Is it possible to fork a Gist to Repo via the GitHub site or client? If not either of those two, can it be done via shell? 解决方案 New Correct AnswerYes, directly!Go to https://github.com/new/import and put in the URL of your gist and a name for your new repo.I just put in https://gist.github.com/RichardBronosky/1aed6606b1283277e7ff9eaa18097e78 and AWS_subnets and it created https://github.com/RichardBronosky/AWS_subnets for me.Important Feature NotesPRO: It keeps all previous commit history including commit messagesMany people don't realize that gist commits may have commit messages that you cannot see with the web interface. The gist above has 2 very decrsiptive commit messages that I commited on my local clone and pushed out. They are hidden from the gist web interface, but show up in clones and also new repos created using this import feature.PRO: It retains gist commits from other authors CON: In spite of #2, it shows only 1 contributor (which is myself).CON: Even though my gist shows "forked from nboubakr/subnet.py", this new/imported github repo does not show that it is a fork of anything (not nboubakr's gist nor my gist)VerdictThis works very well and I really appreciate the PROs. The cons are not enough to make me think that some other method would be better.I will use this extensively in the future because I often create a gist that answers some Stack Overflow question. Then I expand upon it and realize it should be a full repo. Not that I think my work is of great significance, but because I think my commit messages are worth sharing. And this is because I am lazy and tend to not want to create documentation that just repeats what i have already said in commit messages. 这篇关于叉重要GitHub回购的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！