Skip to content
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

Use correct description of detaching a fork #37296

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ocdtrekkie
Copy link

Why:

When I was looking at detaching a fork, I read these docs and when I came across the word "delete" here, I was concerned this might delete my fork instead of detaching it. I believe this part of the documentation was copied from the details about how to delete a repo (or manually detach, which includes deleting the repo), and changing this word was missed.

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

In the section about automatically detaching a fork, I just changed "deleting" to "detaching", since the process described in this section does NOT delete the fork.

Check off the following:

  • A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
  • The changes in this PR meet the docs fundamentals that are required for all content.
  • All CI checks are passing and the changes look good in the review environment.

Copy link

welcome bot commented Apr 4, 2025

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 Apr 4, 2025
Copy link
Contributor

github-actions bot commented Apr 4, 2025

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

A Hubber will need to deploy your changes internally to review.

Table of review links

⚠️ Warning: Our review server is experiencing latency issues.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on the review server. Changes to the data directory are not included in this table.

Source Review Production What Changed
pull-requests/collaborating-with-pull-requests/working-with-forks/detaching-a-fork.md fpt
ghec
ghes@ 3.16 3.15 3.14 3.13 3.12
fpt
ghec
ghes@ 3.16 3.15 3.14 3.13 3.12

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

🤖 This comment is automatically generated.

changeschung

This comment was marked as spam.

@Sharra-writes
Copy link
Contributor

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

@Sharra-writes Sharra-writes added content This issue or pull request belongs to the Docs Content team and removed triage Do not begin working on this issue until triaged by the team labels Apr 4, 2025
@jesesjr
Copy link

jesesjr commented Apr 5, 2025

  "runner_name": "my runner",

@changeschung
Copy link

  "runner_name": "my runner",

Can you help this runner_name?

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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants