Skip to content

Update comparing-commits.md to mention "OWNER:REPO:BRANCH" new pattern - #34927

Merged
nguyenalex836 merged 3 commits into
github:mainfrom
muzimuzhi:comparing-commits
Oct 14, 2024
Merged

Update comparing-commits.md to mention "OWNER:REPO:BRANCH" new pattern#34927
nguyenalex836 merged 3 commits into
github:mainfrom
muzimuzhi:comparing-commits

Conversation

@muzimuzhi

@muzimuzhimuzimuzhi commented Oct 14, 2024

Copy link
Copy Markdown
Contributor

Why:

Closes: #34381

What's being changed (if available, include any code snippets, screenshots, or gifs):

Apply the suggested change in #34381 (comment), with a change of UK spelling "organisation" -> "organization".

Check off the following:

  • I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

    • For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.
  • For content changes, I have completed the self-review checklist.

in the "Comparing across forks" section
@github-actionsgithub-actionsBot added the triage Do not begin working on this issue until triaged by the team label Oct 14, 2024
@github-actions

github-actionsBot commented Oct 14, 2024

Copy link
Copy Markdown
Contributor

Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.


Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

SourcePreviewProductionWhat Changed
pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.mdfpt
ghec
ghes@ 3.143.133.123.113.10
fpt
ghec
ghes@ 3.143.133.123.113.10

fpt: Free, Pro, Team
ghec: GitHub Enterprise Cloud
ghes: GitHub Enterprise Server

You can compare your base repository and any forked repository. This is the view that's presented when a user performs a Pull Request to a project.

To compare branches on different repositories, preface the branch names with user names. For example, by specifying `octocat:main` for `base` and `octo-org:main` for `compare`, you can compare the `main` branch of the repositories respectively owned by `octocat` and `octo-org`.
To compare branches on different repositories, preface the branch names with user names. For example, by specifying `octocat:main` for `base` and `octo-org:main` for `compare`, you can compare the `main` branch of the repositories respectively owned by `octocat` and `octo-org`. You can also preface the branch name with a user name and a repository name. For example, specifying `octocat:awesome-app:main` would use the `main` branch in the `octocat/awesome-app` repository. This can be useful in large organizations, where you might have an upstream repository and a fork both owned by the organization. For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)."

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The paragraph looks a bit long so maybe the newly added sentences can start its own paragraph?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@muzimuzhi Agreed! Feel free to update and I'll get this merged 💛

@Myera2411

This comment was marked as spam.

@nguyenalex836nguyenalex836 added content This issue or pull request belongs to the Docs Content team waiting for review Issue/PR is waiting for a writer's review pull requests Content related to pull requests and removed triage Do not begin working on this issue until triaged by the team waiting for review Issue/PR is waiting for a writer's review labels Oct 14, 2024
@nguyenalex836

nguyenalex836 commented Oct 14, 2024

Copy link
Copy Markdown
Contributor

@muzimuzhi Thanks for that last update! I'll get this merged 💛

@nguyenalex836
nguyenalex836 added this pull request to the merge queueOct 14, 2024
Merged via the queue into github:main with commit bd20a55Oct 14, 2024
@github-actions

Copy link
Copy Markdown
Contributor

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues

@muzimuzhi
muzimuzhi deleted the comparing-commits branch October 15, 2024 02:28
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

contentThis issue or pull request belongs to the Docs Content teampull requestsContent related to pull requests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Mention new "OWNER:REPO:BRANCH" pattern in "Comparing across forks"

3 participants

@muzimuzhi@Myera2411@nguyenalex836