{"push_id":2868956091,"size":3,"distinct_size":3,"ref":"refs/heads/master","head":"0c211fd33b8e0e9defe01c2df6e30e00eb187def","before":"0b6b802076561602a9092f6e5ca4bc0111f87e35","commits":[{"sha":"6203471f11d20bd5f6fbe089f18325c005aaac3d","author":{"name":"Nick Lewis","email":"75ef9faee755c70589550b513ad881e5a603182c@puppetlabs.com"},"message":"(BOLT-719) Log the effective modulepath\n\nThis will help users understand where built-in content is coming from,\nas well as where they should install modules.","distinct":true,"url":"https://api.github.com/repos/puppetlabs/bolt/commits/6203471f11d20bd5f6fbe089f18325c005aaac3d"},{"sha":"9a43ee65f89c5a1e6632dd95788a101a127581f8","author":{"name":"Nick Lewis","email":"75ef9faee755c70589550b513ad881e5a603182c@puppetlabs.com"},"message":"(BOLT-719) Allow modulepath relative to Boltdir\n\nPreviously, relative paths in the bolt.yaml file were treated as\nrelative to pwd, which is almost never what's expected. We now treat\nthem as relative to Boltdir, allowing a modulepath like site:modules to\nbe used to represent .../Boltdir/site:.../Boltdir/modules, regardless of\nwhere the Boltdir is located on disk.\n\nWhen modulepath is specified on the CLI, relative paths are still\ninterpreted as relative to the pwd, which should be less surprising for\nnew users than making it implicitly based on a directory (Boltdir) they\nmay not even know exists.","distinct":true,"url":"https://api.github.com/repos/puppetlabs/bolt/commits/9a43ee65f89c5a1e6632dd95788a101a127581f8"},{"sha":"0c211fd33b8e0e9defe01c2df6e30e00eb187def","author":{"name":"Michael Smith","email":"5fa21ba918749479f1a2164cc11f556766c4eb5f@puppet.com"},"message":"Merge pull request #626 from nicklewis/BOLT-719-relative-modulepath\n\n(BOLT-719) Allow modulepath relative to Boltdir","distinct":true,"url":"https://api.github.com/repos/puppetlabs/bolt/commits/0c211fd33b8e0e9defe01c2df6e30e00eb187def"}]}
{"actor":{"display_login":"MikaelSmith"}}