Closed miki725 closed 3 months ago
all other keys are derived from the commit so if chalk cant figure out correct commit id, rest are descriptions of the commit so I think thats the most critical part to mention in the changelog but we can improve before release if we like
CHANGELOG.md
if necessaryIssue
wrong commit id is reported
Description
.git/HEAD
can be a symbolic ref to a branch/tag or directly pointer to a commit. When doinggit checkout <branch>
it normally sets it to symbolic ref however when doinggit checkout <tag>
it usually sets it directly to the tag's commit. However it is possible to update it viagit symbolic-ref HEAD <tag>
. In that caseHEAD
will point to annotated tag and as such we chalk simply opens the ref of that symbolic ref it is not guaranteed to be for a commit id. Now chalk loads the tag object and if it is an annotated tag, resolves commit id to be from the tags object pointer.Testing