Skip to content

Change release tags from lightweight to annotated #179

@royhills

Description

@royhills

github uses lightweight tags for releases, which makes git describe reference an earlier annotated tag unless the --tags option is specified.

The git-tag manpage states that releases should use annotated tags, so I'm not sure why github uses lightweight tags for this:

Annotated tags are meant for release while lightweight tags are meant for private or temporary object labels. For this reason, some git commands for naming objects (like git describe) will ignore lightweight tags by default

For example, the latest release is 1.10.0 but git describe uses the earlier annotated tag for version 1.9.8 unless --tags is specified:

rsh@bookworm:~/arp-scan$ git tag -l --sort=v:refname
1.4
1.5
1.6
1.7
1.8
1.9
1.9.2
1.9.3
1.9.4
1.9.5
1.9.6
1.9.7
1.9.8
1.10.0
rsh@bookworm:~/arp-scan$ git describe
1.9.8-93-g97e3b76
rsh@bookworm:~/arp-scan$ git describe --tags
1.10.0-45-g97e3b76

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions