将github repo文件迁移到不同项目的Azure Devops Wiki
我在GitHub有一个存储库,那里有很多文档(.md)文件。 我想将文档迁移到Azure Devops Wiki之一中。 我被引用 this 链接。 当我使用选项 以Wiki 发布代码时,它仅显示Azure DevOps项目中可用的存储库。 有什么方法可以将来自另一个项目的存储库中的GitHub文档发布到Azure Devops WikiS中?
I have a repository in GitHub and have a bunch of documentation(.md) files there.
I want to migrate the documentations into one of the Azure DevOps Wikis.
I am referring this link.
When I am using the option Publish code as Wiki,it only shows the repositories which are available inside the Azure DevOps project.
Is there a way I can publish the GitHub documentations in repositories which are from another project into the Azure DevOps Wikis?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
考虑以不同的方式接近这一点。如果您将git用于Azure DevOps项目,则Azure Devops Wiki应该持续到一个隐藏但可定位的Git存储库中。 git克隆源和目标存储库本地。然后将您想要的内容复制到目标(Azure Devops Wiki,本地克隆)。 git添加,提交并推动添加的目标文件。
附加的图像/文件(如果有的话)可能会更有问题,具体取决于它们在源github存储库中的确切表示。在Azure Devops Wiki中,所有附件都简单地存储在root
。Attachments
文件夹中。因此,您需要将它们迁移到那里并“修复”您的链接。我已经做到了另一个方向,azure devops wiki-> Github企业仓库。您应该知道,您可能需要“修复”页面链接,并且两个降价样式可能需要解决一些差异。
Consider approaching this differently. If you are using git for your Azure DevOps project, then the Azure DevOps Wiki should be persisted to a hidden, but locatable, git repository. Git clone the source and target repositories locally. Then copy what you want to the target (Azure DevOps Wiki, local clone). Git add, commit, and push the added target files.
Attached images/files, if any, may be more problematic depending on how exactly they are represented in the source GitHub repo. In Azure DevOps Wiki ALL attachments are simply stored in a root
.attachments
folder. So, you'll need to migrate them there and "fix up" your links.I've done this going the other direction, Azure DevOps Wiki -> GitHub Enterprise repo. You should know that you’ll likely need to “fix up” page links and that the two markdown styles have slight variations you may have to address.