Skip Menu |

This queue is for tickets about the Dist-Zilla-Plugin-Git CPAN distribution.

Report information
The Basics
Id: 78128
Status: open
Priority: 0/
Queue: Dist-Zilla-Plugin-Git

People
Owner: Nobody in particular
Requestors: ether [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: [Git::NextVersion] should accept the tag_format config from [@Git]
[Git::NextVersion]'s documentation says: C<version_regexp> - regular expression that matches a tag containing a version. It must capture the version into $1. Defaults to ^v(.+)$ which matches the default C<tag_format> from L<Dist::Zilla::Plugin::Git::Tag>. If you change C<tag_format>, you B<must> set a corresponsing C<version_regexp>. If one is using the entire bundle, [@Git], the config "tag_format" from [Git::Tag] is also visible to [Git::NextVerion]. In this case, it is possible to automatically populate version_regexp, without getting it wrong (or having to set it explicitly).
But Git::NextVersion is not included in @Git (nor should it be added, because that would break the config of everybody currently using @Git). Also, automatically creating a version_regexp from tag_format wouldn't be trivial (although probably not all that hard).
On Thu Sep 06 18:38:23 2012, CJM wrote: Show quoted text
> Also, automatically creating a version_regexp from tag_format wouldn't > be trivial (although probably not all that hard).
Reopening to track the concept - it's looking like either [@Git] or a new dist can/should create a central stash of git-related configs, that all git plugins can dip into. one reference discussion: https://github.com/RsrchBoy/dist-zilla-pluginbundle-git-checkfor/issues/2
On Fri, Dec 21, 2012 9:49:12 PM, ETHER wrote: Show quoted text
> it's looking like either [@Git] or a > new dist can/should create a central stash of git-related configs, that > all git plugins can dip into.
We already have a bug for that, RT#80010.