Hallo, Entdecker! An dieser Seite wird aktiv gearbeitet, oder sie wird noch übersetzt. Die neuesten und genauesten Informationen finden Sie in unserer englischsprachigen Dokumentation.
Artikelversion: Enterprise Server 2.15

Diese Version von GitHub Enterprise wird eingestellt am Diese Version von GitHub Enterprise wurde eingestellt am 2019-10-16. Es wird keine Patch-Freigabe vorgenommen, auch nicht für kritische Sicherheitsprobleme. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise. For help with the upgrade, contact GitHub Enterprise support.

About comparing branches in pull requests

Pull requests display diffs to compare the changes you made in your topic branch against the base branch that you want to merge your changes into.

Note: When creating your pull request, you can change the base branch that you're comparing your changes against. For more information, see "Creating a pull request."

In this article:

You can view proposed changes in a pull request in the Files changed tab.

Pull Request Files changed tab

Rather than viewing the commits themselves, you can view the proposed changes as they'll appear in the files once the pull request is merged. The files appear in alphabetical order within the Files changed tab. Additions to the files appear in green and are prefaced by a + sign while content that has been removed appears in red and is prefaced by a - sign.

Diff view options

Tip: If you're having a hard time understanding the context of a change, you can click View in the Files changed tab to view the whole file with the proposed changes.

You have several options for viewing a diff:

You can also choose to ignore whitespace changes to get a more accurate view of the substantial changes in a pull request.

Diff viewing options menu

Three-dot and two-dot Git diff comparisons

Pull requests on GitHub show a three-dot diff, or a comparison between the most recent version of the topic branch and the commit where the topic branch was last synced with the base branch.

If you want to see a comparison between the most recent versions of each branch, or a two-dot diff, you can merge the base branch into your working branch to update the last common ancestor.

Reasons diffs will not display

Further reading

Menschliche Unterstützung einholen

Sie können das Gesuchte nicht finden?

Kontakt