Skip to content

Updating add upstream comment#18183

Closed
ramigonzalez wants to merge 1 commit into
github:mainfrom
ramigonzalez:patch-2
Closed

Updating add upstream comment#18183
ramigonzalez wants to merge 1 commit into
github:mainfrom
ramigonzalez:patch-2

Conversation

@ramigonzalez
Copy link
Copy Markdown

@ramigonzalez ramigonzalez commented May 24, 2022

The previous comment was intended to do the same as origin remote was configured

Why:

It closes a miswritten command

What's being changed:

Check off the following:

  • I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
  • For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

  • This pull request impacts the contribution experience
    • I have added the 'writer impact' label
    • I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

The previous comment was intended to do the same as origin remote was configured
@welcome
Copy link
Copy Markdown

welcome Bot commented May 24, 2022

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

@github-actions github-actions Bot added the triage Do not begin working on this issue until triaged by the team label May 24, 2022
@github-actions
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.

Source Preview Production What Changed
get-started/quickstart/fork-a-repo.md fpt
ghec
ghes@ 3.5 3.4 3.3 3.2 3.1
ghae
fpt
ghec
ghes@ 3.5 3.4 3.3 3.2 3.1
ghae

@janiceilene
Copy link
Copy Markdown
Contributor

@ramigonzalez Thanks so much for opening a PR! I'll get this triaged for review ⚡

@janiceilene janiceilene 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 and removed triage Do not begin working on this issue until triaged by the team labels May 26, 2022
@janiceilene
Copy link
Copy Markdown
Contributor

👋 @ramigonzalez I've spoken with team and it looks like the docs say ORIGINAL-OWNER now in https://docs.github.com/en/get-started/quickstart/fork-a-repo#configuring-git-to-sync-your-fork-with-the-original-repository. Is that what you're seeing?

I'm going to close this now, but please let us know if you're still having trouble!

Thanks so much for your interest and passion in improving the GitHub Docs 💖

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

content This issue or pull request belongs to the Docs Content team waiting for review Issue/PR is waiting for a writer's review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Go in

2 participants