Refname ‘master’ is ambiguous

by

TL;DR: save and delete the tag, as Ashutosh Jindal comments (see “Rename a tag in git?“):

git tag tag-master master
git tag -d master

Original answer:

Most of the sources I see (like this FAQ) point to the same cause:

When you try to checkout a local branch, you get a

warning: refname 'branch-name' is ambiguous

This can happen if you’ve created a local branch with the same name as a remote tag.
Git should be checking out your local branch, but instead it’s trying to checkout the tag, and it gets confused.

The initial import of several trees were problematic, since they contained identically named branches and tags. We have since addressed a lot of these issues, by renaming away the tags.

In your case, you don’t have a remote, but local tags named like your branch could be enough.

The ambiguity is specified in gitrevision

<refname>, e.g. master, heads/master, refs/heads/master

A symbolic ref name. E.g. master typically means the commit object referenced by refs/heads/master.
If you happen to have both heads/master and tags/master, you can explicitly say heads/master to tell git which one you mean.
When ambiguous, a <refname> is disambiguated by taking the first match in the following rules:

If $GIT_DIR/<refname> exists, that is what you mean (this is usually useful only for HEAD, FETCH_HEAD, ORIG_HEAD, MERGE_HEAD and CHERRY_PICK_HEAD);

  • otherwise, refs/<refname> if it exists;
  • otherwise, refs/tags/<refname> if it exists;
  • otherwise, refs/heads/<refname> if it exists;
  • otherwise, refs/remotes/<refname> if it exists;
  • otherwise, refs/remotes/<refname>/HEAD if it exists.

So check where master can be found in your repo.

And git checkout heads/master would always work.
Warning: by default, this would checkout the branch in a DETACHED HEAD mode. See “Why does git checkout with explicit ‘refs/heads/branch‘ give detached HEAD?“.

To avoid that, and still use an unambiguous ref, type:

git checkout -B master heads/master

More Related Contents:

  1. What exactly do we mean by “branch”?
  2. git submodule tracking latest
  3. How to sparsely checkout only one single file from a git repository?
  4. Changing capitalization of filenames in Git
  5. How do I resolve git saying “Commit your changes or stash them before you can merge”?
  6. How to configure Git post commit hook
  7. Create a branch in Git from another branch
  8. Resetting remote to a certain commit
  9. Making ‘git log’ ignore changes for certain paths
  10. How do I fetch only one branch of a remote Git repository?
  11. Github file size limit changed 6/18/13. Can’t push now
  12. Trying to understand `git diff` and `git mv` rename detection mechanism
  13. Git excludesfile for a branch
  14. How do you remove an invalid remote branch reference from Git?
  15. Git – Checkout a remote tag when two remotes have the same tag name
  16. How can I solve this invalid credentials problem on Bitbucket?
  17. What’s git’s heuristic for assigning content modifications to file paths?
  18. How do I update my bare repo?
  19. How do I undo a checkout in git?
  20. Adding a collaborator to my free GitHub account?
  21. Which is the smarter git protocol, ssh or git(over ssh) or https protocol?
  22. Mark a file in the GIT repo as temporarily ignored
  23. How can I stage and commit all files, including newly added files, using a single command?
  24. How to get default Git branch?
  25. Git is moving to new hashing algorithm SHA-256 but why git community settled on SHA‑256
  26. Make .git directory web inaccessible
  27. Error in git push heroku master through ssh behind proxy
  28. Restore git submodules from .gitmodules
  29. Can Git treat ZIP files as directories and files inside the ZIP as blobs?
  30. Telling if a Git commit is a Merge/Revert commit

Leave a Comment