Bence Csókás, on Git 2.55.0, noted that git help check-ref-format says branch names cannot be the single character @, and git check-ref-format @ rejects it. Yet git checkout -b @, git switch -c @ and git branch @ all create such a branch, while other invalid names such as master@{1} are rejected with a hint. He considers this a bug.

The discussion moved to the '@' shorthand for HEAD. Junio Hamano said it "conveniently" squats on the name and makes a branch called "@" hard or impossible to use. He called it a poorly designed shorthand that forbids a name which follows the documented rules perfectly well. He also told Csókás he has "some unlearning of a bad habit to do".

D. Ben Knoble pushed back. He said what is short and easy to type suits interactive use, even if scripts should spell out HEAD and long options, and asked what is bad about the habit. He added that Csókás's grep also counted uses such as @{upstream}, @{u}, @{push} and reflog syntax.

Kristoffer Haugsbakk said he had set up git symbolic-ref refs/H HEAD after an earlier conversation about @, and linked that thread.

The thread does not settle whether Git should reject the creation of a branch named '@'.