Skip to content

Add the 'tags'-option to the main example configuration #263

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Oct 5, 2016
Merged

Add the 'tags'-option to the main example configuration #263

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
04e4114
https://github.com/ktoso/maven-git-commit-id-plugin/issues/262: Add t…
Oct 5, 2016
e808f91
Syntax Highlighting does not work in comments :/
Oct 5, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -366,7 +366,16 @@ It's really simple to setup this plugin; below is a sample pom that you may base

<!-- Only consider tags matching the given pattern. This can be used to avoid leaking private tags from the repository. -->
<match>*</match>


<!--
when you run git-describe it only looks only for *annotated tags* by default
if you wish to consider *lightweight tags* in your describe as well you would need to switch this to *true*

The difference between *annotated tags* and *lightweight tags* is outlined in more depth here:
https://github.com/ktoso/maven-git-commit-id-plugin/#git-describe-and-a-small-gotcha-with-tags
-->
<tags>false</tags>

<!--
always print using the "tag-commits_from_tag-g_commit_id-maybe_dirty" format, even if "on" a tag.
The distance will always be 0 if you're "on" the tag.
Expand Down