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

[Improvement]: Duplicate content in description of "private" parameter for Update a Repo endpoint #11784

Open
docs-bot opened this issue Nov 8, 2021 · 2 comments

Comments

@docs-bot
Copy link
Collaborator

@docs-bot docs-bot commented Nov 8, 2021

Is this issue for a product update or release that is not yet available to customers?

No? Then please continue. Thank you!

What article(s) is affected?

https://docs.github.com/en/rest/reference/repos#update-a-repository

Describe the desired docs changes and the problem they solve for customers.

Remove duplicate content.

There is a duplicated statement in the description of the "private" field:

Either true to make the repository private or false to make it public. Default: false.
Note: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private. Note: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private.
Default: false

To fix this, we should remove one of the duplicated sentences.

Who does this affect?

REST API users

What is the impact to users?

It's confusing to have duplicate sentences

Are you willing to open a PR to make this fix? If not, do you know anyone (Hubber or not, we're open source!) who's willing to help write this documentation?

No 😸

@ghost
Copy link

@ghost ghost commented Nov 9, 2021

Remove all duplicate '422' error notes from the REST API docs #11791 TY

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

Successfully merging a pull request may close this issue.

None yet
3 participants
@ramyaparimi @docs-bot and others