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

Docs say operations with https: URLs will ask for authentication, but I think this is only true for private repos #35846

Open
1 task done
dmick opened this issue Jan 7, 2025 · 4 comments
Labels
content This issue or pull request belongs to the Docs Content team more-information-needed More information is needed to complete review rest Content related to rest - overview.

Comments

@dmick
Copy link

dmick commented Jan 7, 2025

Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls

What part(s) of the article would you like to see updated?

I want to verify that https: access only requires authentication for private repos, and if so, change the docs to say so, specifically at least the sentence "When you git clone, git fetch, git pull, or git push to a remote repository using HTTPS URLs on the command line, Git will ask for your GitHub username and password."

Additional information

No response

@dmick dmick added the content This issue or pull request belongs to the Docs Content team label Jan 7, 2025
Copy link

welcome bot commented Jan 7, 2025

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

@dmick
Copy link
Author

dmick commented Jan 7, 2025

I'm happy to file a PR if my assertion is true.

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Jan 7, 2025
@nguyenalex836 nguyenalex836 added waiting for review Issue/PR is waiting for a writer's review rest Content related to rest - overview. and removed triage Do not begin working on this issue until triaged by the team labels Jan 7, 2025
@nguyenalex836
Copy link
Contributor

@dmick Thank you for raising this issue! I'll get this triaged for review ✨ Our team will provide feedback regarding the best next steps for this issue - thanks for your patience! 💛

@subatoi
Copy link
Contributor

subatoi commented Jan 8, 2025

@dmick You're correct here—if possible I'd prefer to keep the change as simple as possible and just add the word "private" to the sentence you pointed to, but I'm open to discussing an alternative solution here if you prefer. I won't mark this as help wanted as you've indicated you'd like to raise a PR yourself. Thank you!

@nguyenalex836 nguyenalex836 added more-information-needed More information is needed to complete review and removed waiting for review Issue/PR is waiting for a writer's review labels Jan 8, 2025
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 more-information-needed More information is needed to complete review rest Content related to rest - overview.
Projects
None yet
Development

No branches or pull requests

3 participants