{"push_id":885735082,"size":2,"distinct_size":2,"ref":"refs/heads/BuildConfigurationEndpoint-clone","head":"d9d3f15eec5acf1b1327a29cfa86da86f6f946ba","before":"5df5966407e2a283085e3e5311eac8ac229a8ffc","commits":[{"sha":"0dc390f535dbfcc95944f0a27736b361d35f78e6","author":{"email":"02c55f18a892b365bcd1802db9e5c9df39c04674@redhat.com","name":"Paul Gier"},"message":"Minor improvement to variable name","distinct":true,"url":"https://api.github.com/repos/thauser/pnc/commits/0dc390f535dbfcc95944f0a27736b361d35f78e6"},{"sha":"d9d3f15eec5acf1b1327a29cfa86da86f6f946ba","author":{"email":"02c55f18a892b365bcd1802db9e5c9df39c04674@redhat.com","name":"Paul Gier"},"message":"[NCL-1475] Require build record sets for each milestone and don't allow updates\n\nA product milestone should always have a two build record sets, one for builds performed\nand one for builds distributed.  The contents of the sets can change over time, but\nthe milestone should never be able to change to a different build record set.\n\nThe model also needs to prevent updates to the product version associated with a milestone","distinct":true,"url":"https://api.github.com/repos/thauser/pnc/commits/d9d3f15eec5acf1b1327a29cfa86da86f6f946ba"}]}