wpf ui github
When you fork someone’s repository on GitHub, you’ll want to update your fork with any changes made to the original. There are various ways to do this. In this quick tip, Bruno describes how to update your fork via the GitHub website. Another option is to update your fork via the command line.
当您在GitHub上分叉某人的存储库时，您将需要使用对原始分叉的任何更改来更新您的分叉。 有多种方法可以做到这一点。 在此快速提示中，Bruno描述了如何通过GitHub网站更新fork。 另一个选择是通过命令行更新fork 。
I often find myself having to update my fork of someone else’s repo to include the changes made to the original since the fork. In fact, we use this approach often in SitePoint’s Peer Review System as well.
我经常发现自己必须更新其他人的仓库的分支，以包含自分支以来对原始仓库所做的更改。 实际上，我们也经常在SitePoint的对等审查系统中使用这种方法。
Purely by accident, I’ve recently discovered a way to quickly and easily sync a fork with the original repo through the GitHub web UI, so no need to go commando (use the command line).
纯粹出于偶然，我最近发现了一种通过GitHub Web UI快速轻松地将派生与原始存储库同步的方法，因此无需使用Commando (使用命令行)。
Note that the approach below does a merge commit, not a proper rebase. If you understand what this means, this is something that will matter to you. In a nutshell, the history looks different than when syncing via the command line as per Github docs. No real effect, but just a heads up!
请注意，以下方法执行合并提交，而不是适当的变基。 如果您了解这意味着什么，那么这对您很重要。 简而言之，历史看上去与根据Github docs通过命令行同步时的历史不同。 没有真正的效果，但请注意！
Here’s a step by step guide, as applied to my out-of-date fork of Gatekeeper:
这是逐步的指南，适用于我过时的Gatekeeper分支：
Go to your own fork’s UI, and click the “New Pull Request” button:
转到您自己的fork的UI，然后单击“ New Pull Request”按钮：
This will take you to a screen not too different from this one:
这将带您进入与此屏幕不太相似的屏幕：
If the option to try “switching the base” is there, click that.
如果有尝试“切换基座”的选项，请单击该选项。
If the option isn’t there, switch the bases manually by using the provided dropdowns, and set them up so that your fork is on the left, and the original is on the right, like so:
如果没有该选项，请使用提供的下拉菜单手动切换底座，然后进行设置，以使叉子位于左侧，而原叉位于右侧，如下所示：
Click the green “Create Pull Request” button. In the input fields that appear, give it a title like “Syncing from original”. Optionally, add a description.
单击绿色的“创建请求请求”按钮。 在出现的输入字段中，为其命名，例如“从原件同步”。 (可选)添加描述。
Again, click the “Create Pull Request” button to actually send the PR. The result should be a typical PR screen:
再次，单击“创建请求请求”按钮以实际发送PR。 结果应为典型的PR屏幕：
Feel free to merge it with the “Merge Pull Request” button (and “Confirm Merge” afterwards), and you’re done!
随时将其与“合并拉取请求”按钮合并(之后再单击“确认合并”)，就完成了！
That’s it – your fork is now in-sync with the changes made to the original, and you can start working on it without fear of conflicts.
就是这样–您的fork现在与对原始文件所做的更改同步，并且您可以开始进行处理而不必担心冲突。
翻译自: https://www.sitepoint.com/quick-tip-sync-your-fork-with-the-original-without-the-cli/
wpf ui github
相关资源：jdk-8u281-windows-x64.exe