blocks|key|324360|text|如何检查它是否为空的？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|324361|正如jberryman在answer+below+(向上投票)中提到的，如果您有权访问远程存储库，则可以在其中运行：|offset|length|324362|git+rev-parse+--is-bare-repository+|code-block|syntax|javascript|324363|它早在commit+493c774,+Git+1.5.3+(9月9日)就推出了。2007)和Matthias+Lederhofer+(matled)的commit+7ae3df8。|style|CODE|324364|当存储库为空时，|324365|输出为"true"，否则为"false“。|blockquote|324366|324367|324368|324369|您可以使用(来自git+config)：|324370|+git+config+--add+push.default+current|324371|指定默认要推送的内容。|324372|或者：|324373|+git+config+--global+push.default+matching|324374|如果你有很多仓库的话。|324375|324376|+current:将当前分支推送到同名分支。|324377|324378|324379|还可以检查警告后面是否没有错误消息，如此SO+question中所示。|324380|324381|因此，您的目标存储库可能是一个空的，但是，正如Sensible+Git+Refspecs中所说的|324382|324383|当您执行git+pull、fetch,+push和其他一些操作时，您需要指定当前存储库的refspec。|324384|324385|refspec描述了本地引用和远程引用之间的映射，因此您可以推送(或拉出等)主分支标头，并将其存储为原始分支标头。基本上，它是一种在repos之间映射分支的方式。|324386|324387|另请参阅"concept+of+bared+shared+repository+in+git“。|324388|324389|注意:与Git1.6.3相比，这是正确的：|324390|默认情况下，会拒绝|324391|+"git+push“到当前已签出的分支。|324392|324393|您可以通过在接收存储库中设置配置变量receive.denyCurrentBranch来选择在这种推送时应该发生什么。|324394|324395|但我不认为这是你现在看到的。|324396|324397|正如在"all+about+"bare"+repos+--+what,+why,+and+how+to+fix+a+non-bare+push“中提到的(在底部)|324398|324399|要使其成为“真正的”纯存储库，只需删除除.git之外的所有文件，然后删除mv+.git/*+.;+rmdir+.git。|324400|324401|最后，编辑名为config+bare+=+false+的文件，并将bare+=+false更改为|BOLD|324402|324403|因此，如果您的目标存储库有一个带有bare++=+true的config文件，那么它就是一个纯存储库。|324404|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/users/176841/jberryman|1|https://stackoverflow.com/a/14734826/6309|2|https://github.com/git/git/commit/493c774e58a05bbbac06e4ae1654ca3d24e4e5cf|3|https://github.com/matled|4|https://github.com/git/git/commit/7ae3df8c0aa3b7337ae9ac7b6184ac05985bf996|5|http://git-scm.com/docs/git-config#_variables|6|https://stackoverflow.com/questions/1475468/git-push-failed-you-did-not-specify-any-refspecs-to-push|7|http://jo3l.net/journal/2009/07/20/sensible-git-refspecs/|8|https://stackoverflow.com/a/24115534/6309|9|http://www.kernel.org/pub/software/scm/git/docs/RelNotes-1.6.3.txt|10|http://htmlpreview.github.io/?https://github.com/sitaramc/sitaramc.github.com/blob/dce410b2a2804723676db9cabd7bb506b6d9ba05/concepts/bare.html^0|0|2|9|0|C|C|1|0|0|1V|6|3|P|2|1A|S|3|23|E|4|0|0|0|0|0|0|8|A|8|A|5|0|0|0|0|0|0|0|0|0|0|K|B|6|0|0|N|L|7|0|0|4|8|D|6|K|4|18|7|0|0|0|7|0|0|5|15|8|0|0|4|8|9|0|0|2|8|0|0|I|P|0|0|0|0|4|1V|A|0|0|K|4|10|N|0|0|7|6|E|C|R|L|7|6|E|C|X|C|0|0|0|1F|H|C|U|6|0^^$0|@$1|2|3|4|5|6|7|39|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|3A|8|@]|9|@$D|3B|E|3C|1|3D]|$D|3E|E|3F|1|3G]]|A|$]]|$1|F|3|G|5|H|7|3H|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|3I|8|@$D|3J|E|3K|M|N]]|9|@$D|3L|E|3M|1|3N]|$D|3O|E|3P|1|3Q]|$D|3R|E|3S|1|3T]]|A|$]]|$1|O|3|P|5|6|7|3U|8|@]|9|@]|A|$]]|$1|Q|3|R|5|S|7|3V|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|3W|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|3X|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|3Y|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|3Z|8|@$D|40|E|41|M|N]]|9|@$D|42|E|43|1|44]]|A|$]]|$1|Y|3|Z|5|H|7|45|8|@]|9|@]|A|$I|J]]|$1|10|3|11|5|6|7|46|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|47|8|@]|9|@]|A|$]]|$1|14|3|15|5|H|7|48|8|@]|9|@]|A|$I|J]]|$1|16|3|17|5|6|7|49|8|@]|9|@]|A|$]]|$1|18|3|-4|5|6|7|4A|8|@]|9|@]|A|$]]|$1|19|3|1A|5|S|7|4B|8|@]|9|@]|A|$]]|$1|1B|3|-4|5|6|7|4C|8|@]|9|@]|A|$]]|$1|1C|3|-4|5|6|7|4D|8|@]|9|@]|A|$]]|$1|1D|3|1E|5|6|7|4E|8|@]|9|@$D|4F|E|4G|1|4H]]|A|$]]|$1|1F|3|-4|5|6|7|4I|8|@]|9|@]|A|$]]|$1|1G|3|1H|5|6|7|4J|8|@]|9|@$D|4K|E|4L|1|4M]]|A|$]]|$1|1I|3|-4|5|6|7|4N|8|@]|9|@]|A|$]]|$1|1J|3|1K|5|S|7|4O|8|@$D|4P|E|4Q|M|N]|$D|4R|E|4S|M|N]|$D|4T|E|4U|M|N]|$D|4V|E|4W|M|N]]|9|@]|A|$]]|$1|1L|3|-4|5|6|7|4X|8|@]|9|@]|A|$]]|$1|1M|3|1N|5|6|7|4Y|8|@$D|4Z|E|50|M|N]]|9|@]|A|$]]|$1|1O|3|-4|5|6|7|51|8|@]|9|@]|A|$]]|$1|1P|3|1Q|5|6|7|52|8|@]|9|@$D|53|E|54|1|55]]|A|$]]|$1|1R|3|-4|5|6|7|56|8|@]|9|@]|A|$]]|$1|1S|3|1T|5|6|7|57|8|@]|9|@$D|58|E|59|1|5A]]|A|$]]|$1|1U|3|1V|5|6|7|5B|8|@]|9|@]|A|$]]|$1|1W|3|1X|5|S|7|5C|8|@$D|5D|E|5E|M|N]]|9|@]|A|$]]|$1|1Y|3|-4|5|6|7|5F|8|@]|9|@]|A|$]]|$1|1Z|3|20|5|6|7|5G|8|@$D|5H|E|5I|M|N]]|9|@]|A|$]]|$1|21|3|-4|5|6|7|5J|8|@]|9|@]|A|$]]|$1|22|3|23|5|6|7|5K|8|@]|9|@]|A|$]]|$1|24|3|-4|5|6|7|5L|8|@]|9|@]|A|$]]|$1|25|3|26|5|6|7|5M|8|@]|9|@$D|5N|E|5O|1|5P]]|A|$]]|$1|27|3|-4|5|6|7|5Q|8|@]|9|@]|A|$]]|$1|28|3|29|5|S|7|5R|8|@$D|5S|E|5T|M|N]|$D|5U|E|5V|M|N]]|9|@]|A|$]]|$1|2A|3|-4|5|6|7|5W|8|@]|9|@]|A|$]]|$1|2B|3|2C|5|6|7|5X|8|@$D|5Y|E|5Z|M|2D]|$D|60|E|61|M|2D]|$D|62|E|63|M|2D]|$D|64|E|65|M|N]|$D|66|E|67|M|N]|$D|68|E|69|M|N]]|9|@]|A|$]]|$1|2E|3|-4|5|6|7|6A|8|@]|9|@]|A|$]]|$1|2F|3|2G|5|6|7|6B|8|@$D|6C|E|6D|M|2D]|$D|6E|E|6F|M|N]|$D|6G|E|6H|M|N]]|9|@]|A|$]]|$1|2H|3|-4|5|6|7|6I|8|@]|9|@]|A|$]]]|2I|$2J|$5|2K|2L|2M|A|$2N|2O]]|2P|$5|2K|2L|2M|A|$2N|2Q]]|2R|$5|2K|2L|2M|A|$2N|2S]]|2T|$5|2K|2L|2M|A|$2N|2U]]|2V|$5|2K|2L|2M|A|$2N|2W]]|2X|$5|2K|2L|2M|A|$2N|2Y]]|2Z|$5|2K|2L|2M|A|$2N|30]]|31|$5|2K|2L|2M|A|$2N|32]]|33|$5|2K|2L|2M|A|$2N|34]]|35|$5|2K|2L|2M|A|$2N|36]]|37|$5|2K|2L|2M|A|$2N|38]]]]

How do I check that it is bare?

As mentioned in the <a href="https://stackoverflow.com/a/14734826/6309">answer below</a> (upvoted) by <a href="https://stackoverflow.com/users/176841/jberryman">jberryman</a>, if you have access to the remote repo, you can run in it:

<pre><code>git rev-parse --is-bare-repository 
</code></pre>

It was introduced as early as <a href="https://github.com/git/git/commit/493c774e58a05bbbac06e4ae1654ca3d24e4e5cf" rel="noreferrer">commit 493c774, Git 1.5.3</a> (Sept. 2007) and <a href="https://github.com/git/git/commit/7ae3df8c0aa3b7337ae9ac7b6184ac05985bf996" rel="noreferrer">commit 7ae3df8</a> by <a href="https://github.com/matled" rel="noreferrer">Matthias Lederhofer (<code>matled</code>)</a>.

<blockquote>
 When the repository is bare print "true", otherwise "false".
</blockquote>

<hr>

You could use (from <a href="http://git-scm.com/docs/git-config#_variables" rel="noreferrer"><code>git config</code></a>):

<pre><code> git config --add push.default current
</code></pre>

to specify what you want to push by default.

or:

<pre><code> git config --global push.default matching
</code></pre>

if you have many repositories.

<blockquote>
 current: push the current branch to a branch of the same name.
</blockquote>

Check also if the warning was not followed by an error message like in this <a href="https://stackoverflow.com/questions/1475468/git-push-failed-you-did-not-specify-any-refspecs-to-push">SO question</a>.

<hr>

So your destination repo may be a bare one, but, as said in <a href="http://jo3l.net/journal/2009/07/20/sensible-git-refspecs/" rel="noreferrer">Sensible Git Refspecs</a>:

<blockquote>
 When you do a <code>git pull</code>, <code>fetch,</code> <code>push</code> and some others you need to specify a <code>refspec</code> for the current repository. 
 A <code>refspec</code> describes the mapping between the local reference and the remote one, so you can push (or pull etc) the master branch head and store it as your origin branch head. Basically it’s a way of mapping branches between repos.
</blockquote>

See also "<a href="https://stackoverflow.com/a/24115534/6309">concept of bared shared repository in git</a>".

<hr>

Note: it is true than from <a href="http://www.kernel.org/pub/software/scm/git/docs/RelNotes-1.6.3.txt" rel="noreferrer">Git1.6.3</a>, :

<blockquote>
 "<code>git push</code>" into a branch that is currently checked out will be refused by default. 
 You can choose what should happen upon such a push by setting the configuration variable <code>receive.denyCurrentBranch</code> in the receiving repository.
</blockquote>

But I do not think this is what you are seeing right now.

<hr>

As mentioned in "<a href="http://htmlpreview.github.io/?https://github.com/sitaramc/sitaramc.github.com/blob/dce410b2a2804723676db9cabd7bb506b6d9ba05/concepts/bare.html" rel="noreferrer">all about "bare" repos -- what, why, and how to fix a non-bare push</a>" (at the bottom)

<blockquote>
 To make it a "real" bare repo, just delete all the files except <code>.git</code>, then <code>mv .git/* .; rmdir .git</code>. 
 Finally, edit the file called <code>config</code> and change <code>bare = false</code> to <code>bare = true</code>.
</blockquote>

So if your destination repo has a <code>config</code> file with <code>bare = true</code>, it is a bare repo.

blocks|key|3289465|text|您收到的消息意味着您的远程存储库是空的(这与是否为空无关)。第一次推送到远程仓库时，需要指定要推送的内容：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3289466|git+push+origin+master|code-block|syntax|javascript|3289467|这会将当前的主分支推送到远程存储库。git+push的后续调用将推送“匹配”分支，即如果远程存储库中有“主”分支，您的本地“主”分支将被推送到该分支。|offset|length|style|CODE|3289468|entityMap^0|0|0|I|8|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

The message you’re getting means that your remote repository is empty (which has nothing to do with being bare). When pushing into a remote repository for the first time you need to specify what to push:

<pre><code>git push origin master
</code></pre>

This will push your current master branch to the remote repository. Subsequent invocations of <code>git push</code> will pushing “matching” branches, i.e. if there’s a “master” branch in the remote repository your local “master” branch will be pushed to it.

blocks|key|326632|text|这听起来不像是你的问题，但实际上回答了你在标题中提出的问题:你可以运行……|type|unstyled|depth|inlineStyleRanges|entityRanges|data|326633|$+git+rev-parse+--is-bare-repository|code-block|syntax|javascript|326634|...to查询存储库是否为空。返回'true‘或'false’。|326635|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

It doesn't sound like that was your problem, but to actually answer the question you asked in the title: you can run...

<pre><code>$ git rev-parse --is-bare-repository
</code></pre>

...to query if a repo is bare or not. Returns 'true' or 'false'.

blocks|key|323783|text|打开.get目录中的config文件并查找bare+=+true。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|323784|entityMap^0|2|4|A|6|L|B|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|O|8|@]|D|@]|E|$]]]|G|$]]

Open the <code>config</code> file in the <code>.get</code> directory and look for <code>bare = true</code>.

blocks|key|3076094|text|试一试|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3076095|+$+git+config+--get+core.bare|code-block|syntax|javascript|3076096|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

try

<pre><code> $ git config --get core.bare
</code></pre>

I'm getting the warning

<pre><code>warning: You did not specify any refspecs to push, and the current remote
warning: has not configured any push refspecs. The default action in this
warning: case is to push all matching refspecs, that is, all branches
warning: that exist both locally and remotely will be updated. This may
warning: not necessarily be what you want to happen.
warning:
warning: You can specify what action you want to take in this case, and
warning: avoid seeing this message again, by configuring 'push.default' to:
warning: 'nothing' : Do not push anything
warning: 'matching' : Push all matching branches (default)
warning: 'tracking' : Push the current branch to whatever it is tracking
warning: 'current' : Push the current branch
</code></pre>

which is (I think) a warning that remote is not bare. Yet I intended remote to be bare, and the directory (which is in the form <code>foo.git</code>) doesn't have a .git directory in it. How do I check that it is bare?

Extra information: The remote repository is on a computer with git 1.5.4.3, and the local repository has git 1.6.3.3. Both machines are Ubuntu - the local one is Karmic Koala, the remote one is an older version.

How do I check if a repository is bare?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我得到了警告warning: You did not specify any refspecs to push, and the current remotewarning: has not configured any push refspecs. The default action in thiswarning:...

问如何检查存储库是否为空的？
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何检查存储库是否为空的？EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何检查存储库是否为空的？
EN