Skip to content
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

Docs question in dist.ini recommendation #13

Open
kenahoo opened this issue Dec 17, 2013 · 1 comment
Open

Docs question in dist.ini recommendation #13

kenahoo opened this issue Dec 17, 2013 · 1 comment

Comments

@kenahoo
Copy link

kenahoo commented Dec 17, 2013

In the Dist::Zilla::Plugin::TravisYML docs, can you explain what the options under [@Git] are for, and why we'd want to use them? It's not clear to me from reading - perhaps it will be clear after I stick that stuff in my file and press "go", but I'd like to understand it first.

@SineSwiper
Copy link
Owner

The allow_dirty option is recommended so that a new building of .travis.yml will be committed to the git branch prior to a release (Git::Commit), and not spit out a "branch is dirty" error (Git::Check). The push_to option is for build branches.

CJM's plugin bundle has more docs on how it works, but I should probably add a few lines of docs myself to explain those.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants