-
Notifications
You must be signed in to change notification settings - Fork 59.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mention new "OWNER:REPO:BRANCH" pattern in "Comparing across forks" #34381
Comments
@muzimuzhi Thank you for opening an issue! I'll get this triaged for review ✨ |
The corresponding API docs may need a similar update, for example the doc of Not sure if there are any similar GraphQL APIs. |
Thanks for opening an issue! We've triaged this issue for technical review by a subject matter expert 👀 |
This is a gentle bump for the docs team that this issue is waiting for technical review. |
@muzimuzhi Thank you for your patience while our SME team reviewed! Upon review, our SMEs found we should add the following sentence to this section https://docs.github.com/en/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits#comparing-across-forks:
I've added the |
Code of Conduct
What article on docs.github.com is affected?
https://docs.github.com/en/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits#comparing-across-forks
What part(s) of the article would you like to see updated?
The section Comparing across forks only mentions the
OWNER:BRANCH
pattern to specify acompare
branch in a three-dot comparison, but recently GitHub started using a newOWNER:REPO:BRANCH
pattern.The new pattern can be found in the URL of "Open pull request" pages. Such pages can be opened by visiting
https://github.com/OWNER/REPO/pull/new/BRANCH
or by clicking the "Open pull request" button in the page of a branch ahead of upstream default branch.For example,
muzimuzhi:docs:gh34381-update-basehead-form
pattern.Additional information
The old form
OWNER:BRANCH
still works, though I don't know which one is preferable by the GitHub.For example, https://github.com/github/docs/compare/main...muzimuzhi:gh34381-update-basehead-form?expand=1 still works.
The text was updated successfully, but these errors were encountered: