This is the view that's presented when a user performs a Pull Request to a project. You can compare your base repository and any forked repository. To learn more about other comparison options, see " About comparing branches in pull requests." Comparing across forks To quickly compare two commits or Git Object IDs (OIDs) directly with each other in a two-dot diff comparison on GitHub, edit the URL of your repository's "Comparing changes" page.įor example, this URL uses the shortened seven-character SHA codes to compare commits f75c5dcc. You can also compare two arbitrary commits in your repository or its forks on GitHub in a two-dot diff comparison. Here's an example of a comparison between two tags. To compare tags, you can select a tag name from the compare drop-down menu at the top of the page. Comparing tagsĬomparing release tags will show you changes to your repository since the last release.įor more information, see " Comparing releases." Here's an example of a comparison between two branches. To compare branches, you can select a branch name from the compare drop down menu at the top of the page. You'll always be taken to the branch comparison view when starting a new pull request. The most common use of Compare is to compare branches, such as when you're starting a new pull request. During a comparison, you can always change your base and compare points by clicking on Edit. Įvery repository's Compare view contains two drop down menus: base and compare.īase should be considered the starting point of your comparison, and compare is the endpoint. We'll demonstrate the power of Compare by looking at the compare page for a fork of the Linguist repo, which is at. To compare different versions of your repository, append /compare to your repository's path.
0 Comments
Leave a Reply. |