{"push_id":804954508,"size":3,"distinct_size":3,"ref":"refs/heads/2.3","head":"318d4a5d8419b9e81baf2fead4749ee97e6a8bfa","before":"198ad859b96eb25f62e9afe2f7f80b3ec037dc56","commits":[{"sha":"3217c65634596dc82f836741b9c4340770c7a663","author":{"email":"7a5e6f27299d2bbd9d04b59d9e8e4f8eab83d8cb@neotechnology.com","name":"Mats Rydberg"},"message":"Remove an implementation from QueryContext","distinct":true,"url":"https://api.github.com/repos/neo4j/neo4j/commits/3217c65634596dc82f836741b9c4340770c7a663"},{"sha":"ab95ed6091ea252ec31b2fa94c6532dbca82b9c7","author":{"email":"7a5e6f27299d2bbd9d04b59d9e8e4f8eab83d8cb@neotechnology.com","name":"Mats Rydberg"},"message":"Force which node the rule planner will expand a merge pattern from\n\nPreviously, a merge pattern would always be expanded from the node which had\nan identifier that was returned first by a Map.values call. This order is not\nwell defined. From now on identifiers are sorted in ascending lexicographical\norder and the first bound one is picked.","distinct":true,"url":"https://api.github.com/repos/neo4j/neo4j/commits/ab95ed6091ea252ec31b2fa94c6532dbca82b9c7"},{"sha":"318d4a5d8419b9e81baf2fead4749ee97e6a8bfa","author":{"email":"883768b6dd2c42aea0031b24be8a2da40fef4b64@neotechnology.com","name":"Andres Taylor"},"message":"Merge pull request #5401 from Mats-SX/2.3-document-merge-order\n\nForce which node the rule planner will expand a merge pattern from","distinct":true,"url":"https://api.github.com/repos/neo4j/neo4j/commits/318d4a5d8419b9e81baf2fead4749ee97e6a8bfa"}]}