[6.2 GitHub - Contributing to a Project] - error "Support for password authentication was removed on August 13, 2021"
还没有人认领这个 Issue。
评估
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 45/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- git, github
调研方向
Start with the source passage containing git push origin slow-blink (6) in the GitHub contribution chapter. Review the surrounding instructions and the linked GitHub authentication guidance, then update the example so it reflects currently supported authentication; done means the source no longer directs readers toward password authentication and the rendered book text is consistent.
由索引模型根据 Issue 内容生成。
描述
There's no existing/similar bug report.
- I have searched the existing issues
This report is about a single actionable bug.
- I'm reporting a single actionable bug
This report is about the ProGit book, version 2, English language.
- This bug is not about a translation or old version
Bug covers book website/pdf
- I confirm the bug is about the book as found on the website/pdf
Problem is present in the Pro Git book on the website?
- This bug also affects the Pro Git book as published on the website.
Which version of the book is affected?
Source files
Describe the bug:
At line:
git push origin slow-blink (6)
Get the error:
emote: Support for password authentication was removed on August 13, 2021.
Steps to reproduce:
user@linux:~/git-folder/blink$ git push origin slow-blink
fatal: cannot exec '/usr/bin/ksshaskpass': No such file or directory
Username for 'https://github.com': user
fatal: cannot exec '/usr/bin/ksshaskpass': No such file or directory
Password for 'https://user@github.com':
remote: Support for password authentication was removed on August 13, 2021.
remote: Please see https://docs.github.com/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls for information on currently recommended modes of authentication.
fatal: Authentication failed for 'https://github.com/tonychacon/blink/'
Expected behavior:
Authenticate with smart http
Screenshots:
No response
Additional context:
No response
Device
No response
Operating system
No response
Browser/application + version
No response
- 主要语言
- CSS
- 星标
- 6.6k
- 派生
- 2.1k
- PR 合并指标
- 30 天内没有已合并 PR
贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
progit/progit2 的其他 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
-
bug
难度 2/5 1-3 小时 新手友好度 72/100
-
bug
难度 2/5 1-3 小时 新手友好度 68/100
-
enhancement
难度 1/5 1 小时以内 新手友好度 82/100
-
enhancement
难度 1/5 1-3 小时 新手友好度 65/100
相似的 Issue
-
agent-ready documentation needs-triage
难度 1/5 1-3 小时 新手友好度 88/100
-
untriaged
难度 1/5 1 小时以内 新手友好度 88/100
dotnet/dotnet-api-docs#13095 ·
-
documentation
难度 1/5 1 小时以内 新手友好度 91/100
-
workflow-status page template still says reusable workflows are "triggered only by workflow_call:" 未关闭
难度 1/5 1 小时以内 新手友好度 92/100
-
refactor
难度 2/5 1-3 小时 新手友好度 78/100