Skip to content

fixes the confusing wording in docs making it more clear#45101

Open
Abdulshuu wants to merge 1 commit into
github:mainfrom
Abdulshuu:fixing-docs
Open

fixes the confusing wording in docs making it more clear#45101
Abdulshuu wants to merge 1 commit into
github:mainfrom
Abdulshuu:fixing-docs

Conversation

@Abdulshuu

Copy link
Copy Markdown

Closes: #44811

#44811

fixes issue of making the docs more clear stating "You do not need permission from the upstream repository to push to a fork of it you created." to "You do not need permission from the upstream repository to push to a fork that you created."

@github-actions github-actions Bot added the triage Do not begin working on this issue until triaged by the team label Jul 10, 2026
@github-actions

Copy link
Copy Markdown
Contributor

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

Note: Please update the URL for your staging server or codespace.

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

Source Review Production What Changed
pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md fpt
ghec
ghes@ 3.21 3.20 3.19 3.18 3.17
fpt
ghec
ghes@ 3.21 3.20 3.19 3.18 3.17

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

🤖 This comment is automatically generated.

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

Labels

triage Do not begin working on this issue until triaged by the team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

pull-requests/getting-started/about-collaborative... poor phrasing correction

1 participant