-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support git-describe #31
Comments
@nathansgreen @n0mer Resolved via #32 ? |
@izeye @nathansgreen fixed in 1.4.18 |
I compared the generated value for git.commit.id.describe and the values from "git describe" command and the git-commit-id-maven-plugin The "git describe" command and the git-commit-id-maven-plugin generated the same value and they are different to the value from this Gradle plugin. So I'd like to reopen this issue to review/update the implementation for git.commit.id.describe to make sure we are generating the same value as "git describe" and git-commit-id-maven-plugin. |
* Fix issue #31 (Support git-describe)
maven-git-commit-id-plugin
supportsgit-describe
. In particular, it supports marking "dirty" working copies, so it's clear whether a given build was from a completely clean checkout. Any modification to a committed file will produce a dirty state, leading to a build that may not be reproducible.The text was updated successfully, but these errors were encountered: