{"issue":{"state":"closed","created_at":"2011-12-05T08:45:32Z","updated_at":"2011-12-06T03:29:59Z","user":{"gravatar_id":"7e945991d1d70075cff59331d72ef4d8","id":305339,"url":"https://api.github.com/users/patcon","login":"patcon","avatar_url":"https://secure.gravatar.com/avatar/7e945991d1d70075cff59331d72ef4d8?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"comments":5,"body":"heavywater/pennyworth#14\r\n\r\nThe above issue made me realize that there might be a deficiency to removing the `cookbooks` dir from `.gitignore`, in that if there are submodules in the `cookbooks-sources` directory, their `.git` folders are pulled in, and this gets messy. Would some sort of per-cookbook strip option be possible?\r\n\r\n```\r\ncookbook 'mycookbook',\r\n  :path => 'cookbooks-sources',\r\n  :exclude => [ \".git\" ]\r\n```\r\n\r\nThoughts?","assignee":null,"id":2446801,"number":25,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"labels":[],"title":"Add option for :path to strip .git dir (when pulling in submodule)","html_url":"https://github.com/applicationsonline/librarian/issues/25","closed_at":"2011-12-05T15:29:34Z","url":"https://api.github.com/repos/applicationsonline/librarian/issues/25","milestone":null},"action":"created","comment":{"created_at":"2011-12-06T03:29:58Z","updated_at":"2011-12-06T03:29:58Z","user":{"gravatar_id":"7e945991d1d70075cff59331d72ef4d8","id":305339,"url":"https://api.github.com/users/patcon","login":"patcon","avatar_url":"https://secure.gravatar.com/avatar/7e945991d1d70075cff59331d72ef4d8?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"body":"Just writing a cookbook for freight now, and coming across a good reason to use submodules and librarian-chef together. Thought I'd explain:\r\n\r\nWhenever I'm building a new cookbook, I start a vagrant env repo called `cookbookname-cooking`. I don't push this publicly, but I immediately push a `chef-cookbookname`  skeleton repo public. I then pull that in and begin dev. If it were added as a simple git, then say I get writing and realize I need to add a `require_receipe \"apache2\"` or whatever. So I add this, and then go to add apache2 cookbook to the Cheffile.\r\n\r\nNow if I understand correctly, I'd need to push my changes even if I'm not ready, or `librarian-chef update` and `librarian-chef install` will overwrite my work. This is inconvenient. If I have this in-progress `chef-cookbookname` repo in a submodule that's pulled in from `cookbooks-sources`, then I can run `librarian-chef` commands as I develop, and librarian doesn't get in my way.\r\n\r\nIs this an example of a reason to use submodule, or am I missing a feature of librarian? Hopefully this use-case is helpful for you too :)","id":3027770,"url":"https://api.github.com/repos/applicationsonline/librarian/issues/comments/3027770"}}