Distinguish between tags and branches about node-gitteh HOT 5 CLOSED

A reference points to a commit (or another reference).
It can't be a commit. getReference() returns references, not commits.

There are two types of references:

• Tags are meant to not change. They're found under refs/tags
• Branches are meant to always point to the latest commit. They're found under refs/heads.

There's also a special reference HEAD, that points to what you last checked out.
If you're working on branch master, HEAD will point to refs/heads/master, which will point to some commit.

So the title of the issue should be: Distinguish between tags and branches.
You found another bug: resolve() fails on a tag.

from node-gitteh.

Duly noted and updated. :-)

from node-gitteh.

@balor, just by curiosity, can you post the error when you call resolve()?
Also, are you installing by NPM or cloning the source?

from node-gitteh.

@jmendeth: here's a gist that will reproduce the issue: https://gist.github.com/6725caa86c012c4c6d64

from node-gitteh.

@blalor While probably not helpful to you now, I'll note that gitteh 0.17.x is a refactor and approaches refs a bit differently.

gitteh.References don't actually have a resolve() method in their latest incarnation (this can manually be achieved right now by recursively resolving the reference target until direct is true), however they will eventually. The difference now is when you use gitteh.object to resolve the reference target to a gitteh Object, there is a property called type that will determine whether you're looking at a commit, or a heavyweight Tag object.

from node-gitteh.