NAME

Dist::Zilla::PluginBundle::Author::DOHERTY - configure Dist::Zilla like DOHERTY

VERSION

version 0.32

SYNOPSIS

# in dist.ini
[@Author::DOHERTY]

DESCRIPTION

Dist::Zilla::PluginBundle::Author::DOHERTY provides shorthand for a Dist::Zilla configuration that does what Mike wants.

USAGE

Just put [@Author::DOHERTY] in your dist.ini. You can supply the following options:

Default is false.

Default is none.

Default is none.

Default is %v%t.

Default is ^(v.+)$.

Default is true.

Default is false.

Default is Changes.

Default is origin.

- `github` is a boolean specifying whether to use the plugins
[Dist::Zilla::Plugin::GitHub::Meta](http://search.cpan.org/perldoc?Dist::Zilla::Plugin::GitHub::Meta) and [Dist::Zilla::Plugin::GitHub::Update](http://search.cpan.org/perldoc?Dist::Zilla::Plugin::GitHub::Update).
- `critic_config` is a filename to pass through to [Dist::Zilla::Plugin::Test::Perl::Critic](http://search.cpan.org/perldoc?Dist::Zilla::Plugin::Test::Perl::Critic).
- `googlecode_project` tells [UploadToGoogleCode](http://search.cpan.org/perldoc?Dist::Zilla::Plugin::UploadToGoogleCode)
which project to upload to. This is required if you want to upload your release
to Google Code.
- `fork_is_authoritative` tells [GitHub::Meta](http://search.cpan.org/perldoc?Dist::Zilla::Plugin::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.
- `release_to` is a string that specifies where to send the release. Valid release
targets are:
- PAUSE (or CPAN)

We'll use [UploadToPAUSE](http://search.cpan.org/perldoc?Dist::Zilla::Plugin::UploadToCPAN) to do the release,
and clean up afterwards. This is the default

- GoogleCode

Well use [UploadToGoogleCode](http://search.cpan.org/perldoc?Dist::Zilla::Plugin::UploadToGoogleCode) to do the
release, and clean up afterwards. Make sure you set `googlecode_project`

- local

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.

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 github and twitter to false; sets push_to to an empty array ref (ie: don't push anywhere); and sets release_to to local.

ENVIRONMENT

If true, doesn't add TestRelease or CheckExtraTests.

SEE ALSO

[Dist::Zilla](http://search.cpan.org/perldoc?Dist::Zilla)

configure

mvp_multivalue_args

AVAILABILITY

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/.

BUGS AND LIMITATIONS

You can make new bug reports, and view existing ones, through the web interface at http://rt.cpan.org.

AUTHOR

Mike Doherty doherty@cpan.org

COPYRIGHT AND LICENSE

This software is copyright (c) 2010 by Mike Doherty doherty@cpan.org.

This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.