{"push_id":1239868403,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"33bbd1cb27de9b62f88d7f7714286cfef3965254","before":"8919bd12f30fa820c7c0305c2e225830ccaeed26","commits":[{"sha":"7e1b66a2cb5989098295c6f38813264bbcfacfa3","author":{"name":"Eric Wiseblatt","email":"1536d2105bb2f3f16c2aa164996a7ad4e9daf4ba@google.com"},"message":"Added base.ExecutionContext\n\nThis is a basic API for now, but will likely change over the next CL or two.\nAn execution context is essentially a dictionary, but can have some of its\nelements snapshotted. The dictionary is passed through APIs in the test\nexecution flow, acting as a data store for parameters so that runtime data\nvalues can be exchanged among different methods using predetermined keys,\nthus implementing variables. This can be used to specify contracts involving\nspecific resources generated in the operation whose exact names are not known\nahead of time.\n\nInitially the context is only used in contract validation, but that is just\nto keep the CL smaller. It is an optional parameter in the run_test_case\nmethod used by every test so that we dont need to modify every test in this\nCL. However eventually these tests will explicitly pass in the context and\nthe parameter will become required.","distinct":true,"url":"https://api.github.com/repos/ewiseblatt/citest/commits/7e1b66a2cb5989098295c6f38813264bbcfacfa3"},{"sha":"33bbd1cb27de9b62f88d7f7714286cfef3965254","author":{"name":"Eric Wiseblatt","email":"1536d2105bb2f3f16c2aa164996a7ad4e9daf4ba@google.com"},"message":"Merge pull request #195 from ewiseblatt/3_operation_context\n\nAdd base.ExecutionContext parameter to contract verification","distinct":true,"url":"https://api.github.com/repos/ewiseblatt/citest/commits/33bbd1cb27de9b62f88d7f7714286cfef3965254"}]}
{"actor":{"display_login":"ewiseblatt"}}