repo best practice?

[Guy Matz]

Hello!  Anyone have thoughts on how to best organize a repo for ansible?  One big'un vs repo per role, etc?

Thanks!

[Michael DeHaan]

I generally like, for internal stuff, less repos than more, as it more easily faciliates rearranging things without history, and reduces the number of git commands involved and things to manage.  Also allows commits spanning roles to have better history.

(Public roles for galaxy do require one per repo right now, because that makes it easier to work with the git backend)

On Tue, Sep 16, 2014 at 9:17 AM, Guy Matz <gm...@matz.org> wrote:

Hello!  Anyone have thoughts on how to best organize a repo for ansible?  One big'un vs repo per role, etc?

Thanks!

--
You received this message because you are subscribed to the Google Groups "Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ansible-proje...@googlegroups.com.
To post to this group, send email to ansible...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CABnTgtVRn5v537q%2BMq778%2BBuP1z38THAuD__MxZsed6AuynpBA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.