git:info: detecting host provider for ‘https://gitee.com/‘...
git使用中每次都会弹出多个提示信息:
info: detecting host provider for 'https://gitee.com/'...
倒也不是大问题,但看着不舒服
参考这个大佬的解答
https://code.fitness/post/2022/01/git-detecting-host-provider.html
If ever you see a message such as:
"info: detecting host provider for 'https://git.xxx.ch/'..."
you can tell git
to use the generic provider when accessing your repository (in my example git.xxx.ch
), so that it no longer has to probe it every time:
git config --global credential.git.xxx.ch.provider generic
然后修改如下:把git.xxx.ch改为gitee.com,这里我只针对单个项目进行测试,没有添加global参数
git config credential.gitee.com.provider generic
查看修改结果
git config --list|findstr providercredential.gitee.com.provider=generic
//上面这行结果在修改前config里是没有的
OK了
git:info: detecting host provider for ‘https://gitee.com/‘...相关推荐
- Git报错:fatal: Authentication failed for ‘https://gitee.com/.......‘
提交代码到码云,Git报错如下: Gavin: Incorrect username or password (access token) fatal: Authentication failed f ...
- Git报错:fatal: Authentication failed for https://gitee.com
这句话的意思是:认证失败 原因:用户名或密码错误 解决方法:重置用户名密码 git config --system --unset credential.helper 之后再提交即可
- git push失败:Unable to access 'https://gitee.com/Lmui/proxy.git/': Could not resolve host: gitee.com
Unable to access 'https://gitee.com/Lmui/proxy.git/': Could not resolve host: gitee.com 找到Git/etc文件下 ...
- Git-fatal: unable to access ‘https://gitlab.XX.git/‘: Could not resolve host: gitlab.XX.com.cn
克隆,提交代码 时报错如下: fatal: unable to access 'https://gitlab.XX.git/': Could not resolve host: gitlab.XX.c ...
- hexo提交报错 unable to access ‘https://github.com/*/*.github.io.git/‘: Couldn‘t resolve host ‘github.com
title: >- hexo提交报错 unable to access 'https://github.com//.github.io.git/': Couldn't resolve host ...
- 关于git的fatal: unable to access ‘https://gitee.com/‘: Could not resolve host: gitee.com; Unknown error
关于GIT 的 fatal: unable to access 'https://gitee.com/项目名称/ceshi.git/': Could not resolve host: gitee.c ...
- fatal: unable to access ‘https://github.com/.../.git‘: Could not resolve host: github.com解决方法【亲测有效】
fatal: unable to access 'https://github.com/.../.git': Could not resolve host: github.com解决方法 1.问题原因 ...
- charles抓取iphone https包报错:SSLHandshake: Remote host closed connection during handshake
按照此方法:https://blog.csdn.net/lyhDream/article/details/53178118 在iphone上安装了charles的证书,在charles上也设置了ht ...
- iOS开发:GitHub上传代码错误提示fatal: Authentication failed for 'https://gitee.com/XXX/XXX.git/‘的解决方法
上传代码到Git上面,有时候会遇到各种情况,有些时候是因为合并代码冲突,有些时候是因为修改了Git的登录密码需要重新认证.那么这里就来讲解错误提示fatal: Authentication faile ...
- fatal: 无法访问 ‘https://gitlab.com/libeigen/eigen.git/‘:Failed to connect to gitlab.com port 443: 没有到主机
在安装openmvs 时需要安装eigen, git clone https://gitlab.com/libeigen/eigen.git --branch 3.2 但是一直报错fatal: 无法访 ...
最新文章
- 关于生命、宇宙和万事万物的42个终极问题
- Go并发编程之美-Load/Store操作
- (chap1 网络基础知识)网络的构成要素:(7)网关
- 用 Arthas 神器来诊断 HBase 异常进程
- python网络爬虫系列(六)——数据提取 lxml模块
- 幼儿园计算机课程名称,幼儿园课程建设30:计算机与幼儿园课程的整合(3)
- Android开始中的OOM异常
- 中职计算机老师培训总结报告,中职计算机教师个人工作总结范文5篇.doc
- 原创Netty学习系列导航
- # 20175333曹雅坤 第八周课程学习总结
- 单片机原理与应用技术
- Android蓝牙完全学习手册
- 移动前端开发跟Web前端开发一样吗?有什么区别?
- 【蓝桥杯2014C/C++B组省赛真题】——史丰收速算
- KylinV10上qt5.9开发应用打包步骤(四)--linuxdeployqt源码编译
- python代码怎么换行继续写_python代码太长怎么换行
- 总结!Github年度最强Python库排行榜
- 交通局信息上报“二次录入”难题交给博为小帮!
- Lua性能优化—Lua内存优化
- sql常见语法_常见SQL语法错误以及解决方法