Dist::Zilla::Plugin::Git::NextRelease - Use time-stamp from Git instead of process start time.
This module acts as a moderately thin wrapper to
so that the time-stamps produced are generated by asking
git for the time-stamp of the current branch.
If you always require a specific branch for generating time-stamps, it can be specified as a parameter.
+branch = master
+default_branch = master
( The latter only having impact in detached-head conditions )
This exists mostly because of my extensive use of
[Git::CommitBuild], to provide
a commit series for both releases, and builds of all changes/commits in order to push them to Travis for testing. ( Mostly,
because testing a build branch is substantially faster than testing a master that requires
Dist::Zilla, especially if you're
doing "Fresh install" testing like I am. )
This is the sole method of
[NextRelease] that we override,
in order for it to inject the right things.
This method basically returns the date string to append to the Changes header.
If set, always use the specified branch to determine time-stamp.
Default value is resolved from determining "current" branch.
If you want being on a branch to always resolve to that branch, but you still want a useful behavior when on a detached head, specifying this value means that on a detached head, the stated branch will be used instead.
[Git::NextRelease] enhances and adds a few features of
%d- A CLDR formatter of the
HEADtimestamp. ( Original uses simply
%H- The SHA1 of
%h- The SHA1 of
HEADshortened to 7 characters.
Kent Fredric firstname.lastname@example.org
COPYRIGHT AND LICENSE
This software is copyright (c) 2014 by Kent Fredric email@example.com.
This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.