New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pod::Weaver::Section::Contributors author dependency not declared #15
Comments
Thanks for raising this. I hit the same problem recently when I was setting up a new machine. I don't know why
didn't pull in the distribution. After some further research I've decided to take the belt and braces approach by also including a 'magic comment':
This was recently pushed to master, but not release. |
- add scripts for BuildKite testing - dzil: Replace NoTabsTests with Test::NoTabs - fix #15: Use magic comment to crowbar in an essential dependency - add magic comments for other author dependencies that aren't auto-detected - Add *skeleton* POD for methods This is a shockingly lazy way for me to get my dist to pass Pod::Coverage tests - re-arrange POD in file; so method POD appears in a sensible location - add (markdown) section of POD for build status to show (in github/README.mkdn)
- add scripts for BuildKite testing - dzil: Replace NoTabsTests with Test::NoTabs - fix #15: Use magic comment to crowbar in an essential dependency - add magic comments for other author dependencies that aren't auto-detected - Add *skeleton* POD for methods This is a shockingly lazy way for me to get my dist to pass Pod::Coverage tests - re-arrange POD in file; so method POD appears in a sensible location - add (markdown) section of POD for build status to show (in github/README.mkdn)
… in a GH comment of the same issue chizmw/plack-middleware-xsrfblock#15
I'm not sure what you mean by "didn't pull in the distribution", because |
Note that Pod::Weaver::Section::Contributors is optional when using the ContributorsFromGit plugin; it is not demanded by
dzil authordeps
, but appears to be a requirement to build.The text was updated successfully, but these errors were encountered: