{"push_id":2869304969,"size":1,"distinct_size":1,"ref":"refs/heads/patch-1","head":"5e29f607aed526034013d0e03ef0bd55b456742d","before":"9fb0e32f4490e81d0e81d45e9b455cad11401af3","commits":[{"sha":"5e29f607aed526034013d0e03ef0bd55b456742d","author":{"name":"Ryan O'Meara","email":"844a60a370502ad3233b476b1ac40fc8fb8d24a8@live.com"},"message":"Clarify what is considered a 3rd-party dependency\n\nThe dependencies specified for inclusion in the lib directory were previously phrased as \"third party dependencies\". This usually refers to any libraries in a project, which would include the Azure Java library. I noticed when working with the Maven example that it included all dependencies except the Azure Java library. Since the function is running within Azure, I assume this is due to it being provided automatically. \r\nThis change adds a line clarifying that the Azure Java library is provided and its omission from the lib directory is expected.","distinct":true,"url":"https://api.github.com/repos/romeara/azure-docs/commits/5e29f607aed526034013d0e03ef0bd55b456742d"}]}
{"actor":{"display_login":"romeara"}}