{"thread":{"id":"19790","subject":"Bug: receive.denyCurrentBranch fails if core.bare unset","startedAt":"2009-06-12T15:53:18Z","lastAt":"2009-06-12T15:53:18Z","messageCount":1,"participants":["Alban Crequy"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"116165","messageId":"20090612185318.42e738c6@alban.research.nokia.com","threadId":"19790","inReplyTo":null,"subject":"Bug: receive.denyCurrentBranch fails if core.bare unset","fromName":"Alban Crequy","fromEmail":"alban.crequy@collabora.co.uk","sentAt":"2009-06-12T15:53:18Z","receivedAt":"2009-06-12T15:53:18Z","isPatch":false,"sender":{"key":"alban.crequy@collabora.co.uk","avatar":null},"body":"Hi,\n\nWhen I set \"receive.denyCurrentBranch\" to \"refuse\", it still have the\nbehavior of ignore. On newly created repository, core.bare is always\nset, but I had a old non-bare repository where it is unset. With\ncore.bare unset, rev-parse --is-bare-repository returns true in .git,\nbut false in the worktree.\n\nWhat should be the right fix for this problem? Adding in the\ndocumentation of receive.denyCurrentBranch that setting\ncore.bare explicitely is highly recommended ?\n\nBr,\nAlban\n"}]}