> dzil

Plugin Catalog - after-release

AfterRelease plugins run only when you run dzil release. They perform housekeeping tasks after the release has been made.

CopyMakefilePLFromBuildby ROKR(also tagged: version-control)

This plugin will automatically copy the Makefile.PL from the build directory into the distribution directory so you can commit it to version control. When building directly from GitHub (via cpanm, for example) you would need a Makefile.PL.

CopyReadmeFromBuildby ROKR(also tagged: version-control)

This plugin will automatically copy the README from the build directory into the distribution directory so you can commit it to version control. GitHub, for example, likes to see a README. As an alternative, you can have a separate file (e.g. README.md) for GitHub.

Git::Commitby JQUELIN(also tagged: changelog, git, version-control)

Once the release is done, this plugin will record this fact in Git by committing the changelog and dist.ini.

Git::CommitBuildby JQUELIN(also tagged: git, version-control)

Once the build is done, this plugin will commit the results of the build to a branch that is completely separate from your regular code branches (i.e. with a different root commit). This potentially makes your repository more useful to those who may not have Dist::Zilla and all of its dependencies installed.

Git::Pushby JQUELIN(also tagged: git, version-control)

Once the release is done, this plugin will push the current Git branch and tags to your configured remote.

Git::Tagby JQUELIN(also tagged: before-release, git, version-control)

Once the release is done, this plugin will record this fact in Git by creating a tag. It also checks before a release to ensure that tag doesn't already exist (which would indicate you're trying to release the same version twice).

NextReleaseby RJBS(also tagged: changelog, core, file-munger)

This plugin automatically inserts the version number and release date into your Changes when you make a release.

You can fork and improve this documentation on GitHub!