{"push_id":1603817298,"size":2,"distinct_size":1,"ref":"refs/heads/master","head":"614d10d4420895f9b657f3665ebb65ca362c4adc","before":"2ef1c9d08ddc2e55f7fc95e8483cd71f109d989a","commits":[{"sha":"1c46b4786211fda091e7a67749cf3f98d1b2e52a","author":{"name":"Mat Moore","email":"5aafce608516d8eb949cb92e3eb191d1950e2ce1@digital.cabinet-office.gov.uk"},"message":"Don't lint release branches\n\nWe lint changes by taking the diff with master. This works for dev branches but\nnot release branches, which are either behind or in sync with master.\n\nWhen the commits on the current branch are already in master, diffing it to\nmaster makes no sense.  govuk-lint-ruby picks up lines that wouldn't have been\nlinted when the changes in it were first made.  This is happening for the\ndeployed-to-production branches of our apps, and leads to a lot of spurious\nlint errors when changing the content schemas, because we trigger CI jobs using\nproduction app code with the new schemas.\n\nThis is the same situation as described in https://github.com/alphagov/govuk-puppet/pull/5396","distinct":false,"url":"https://api.github.com/repos/alphagov/govuk-puppet/commits/1c46b4786211fda091e7a67749cf3f98d1b2e52a"},{"sha":"614d10d4420895f9b657f3665ebb65ca362c4adc","author":{"name":"Mat","email":"386aabb46488f62471267b7b2b44f2424b8f749a@users.noreply.github.com"},"message":"Merge pull request #5587 from alphagov/dont-lint-release-branches\n\nDon't lint release branches","distinct":true,"url":"https://api.github.com/repos/alphagov/govuk-puppet/commits/614d10d4420895f9b657f3665ebb65ca362c4adc"}]}
{"actor":{"display_login":"MatMoore"}}