- COMMAND LINE OPTIONS
- SEE ALSO
- BUGS AND LIMITATIONS
- COPYRIGHT AND LICENSE
Dist::Zilla::PluginBundle::Author::DOHERTY - configure Dist::Zilla like DOHERTY
# in dist.ini [@Author::DOHERTY]
Dist::Zilla::PluginBundle::Author::DOHERTY provides shorthand for a Dist::Zilla configuration that does what Mike wants.
[@Author::DOHERTY] in your dist.ini. You can supply the following options:
Default is false.
enable_testsis a comma-separated list of testing plugins to add to
Default is none.
disable_testsis a comma-separated list of testing plugins to skip in
Default is none.
tag_formatspecifies how a git release tag should be named. This is passed to
version_regexpspecifies a regexp to find the version number part of a git release tag. This is passed to
Default is true.
surgicalsays to use Dist::Zilla::Plugin::SurgicalPodWeaver.
Default is false.
max_target_perlis the highest minimum version of perl you intend to require. This is passed to Dist::Zilla::Plugin::Test::MinimumVersion, which generates a minimum-version.t test that'll warn you if you accidentally used features from a higher version of perl than you wanted. (Having a lower required version of perl is okay.)
changelogis the filename of the changelog.
Default is Changes.
push_tois the git remote to push to; can be specified multiple times.
critic_configis a filename to pass through to Dist::Zilla::Plugin::Test::Perl::Critic.
googlecode_projecttells UploadToGoogleCode which project to upload to. This is required if you want to upload your release to Google Code.
fork_is_authoritativetells GitHub::Meta that your fork is authoritative. That means that the repository, issues, etc will point to your stuff on github, instead of wherever you forked from. This is useful if your repository on Github is a fork, but you have taken over maintaining the module, so people should probably send bug reports to you instead of the original author, and should fork from your repo, etc.
github_metadata_remotetells GitHub::Meta that this is the Github repository from which to take metadata. This can be freely combined with
fork_is_authoritativeto control whether we "follow the symlink" if the repo this points to is a fork. By default, the repo will be extracted from the url for the
release_tois a string that specifies where to send the release. Valid release targets are:
PAUSE (or CPAN)
We'll use UploadToPAUSE to do the release, and clean up afterwards. This is the default
Well use UploadToGoogleCode to do the release, and clean up afterwards. Make sure you set
We will do all the releasey things like tagging and pushing and whatnot, but we won't do any releasing things, and we won't clean up. This leaves the release tarball sitting there for you to do with as you will.
In the future, there might be an option to scp the tarball somewhere.
strict_versionset options in Dist::Zilla::PluginBundle::TestingMania, which passes them along to Dist::Zilla::Plugin::Test::Version and thus Test::Version. They set
sharedirindicates which directory is your dist's share directory. The default is share.
COMMAND LINE OPTIONS
Do a fake release.
Specify release targets - can be specified multiple times.
Don't do things that need a network connection: sets
push_toto an empty array ref (ie: don't push anywhere); and sets
The project homepage is http://metacpan.org/release/Dist-Zilla-PluginBundle-Author-DOHERTY/.
The latest version of this module is available from the Comprehensive Perl Archive Network (CPAN). Visit http://www.perl.com/CPAN/ to find a CPAN site near you, or see https://metacpan.org/module/Dist::Zilla::PluginBundle::Author::DOHERTY/.
The development version is on github at http://github.com/doherty/Dist-Zilla-PluginBundle-Author-DOHERTY and may be cloned from git://github.com/doherty/Dist-Zilla-PluginBundle-Author-DOHERTY.git
BUGS AND LIMITATIONS
You can make new bug reports, and view existing ones, through the web interface at https://github.com/doherty/Dist-Zilla-PluginBundle-Author-DOHERTY/issues.
Mike Doherty <firstname.lastname@example.org>
COPYRIGHT AND LICENSE
This software is copyright (c) 2010 by Mike Doherty <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.