{"push_id":697827912,"size":2,"distinct_size":0,"ref":"refs/heads/release","head":"5ade0c775e4275129dbcf73c9bd33d610f06b883","before":"4f33108a87b200c5d1086cbc4da248b3ef82edd1","commits":[{"sha":"322bb263f56435bb229b9954a676c35d276de20c","author":{"email":"a60a20ed872330fa60413bd5d4ca7fac0d528ee0@digital.cabinet-office.gov.uk","name":"David Singleton"},"message":"Set name fields for filtered facets\n\nOtherwise the label of the option select is blank, which is bad.\n\nThis is a quick fix so we can deploy these facets properly, but\nthere is an underlying issue, in part because we have quite a few\nname-like fields on facets (name, short name, preposition)\n\nThoughts on longer term fixes:\n\n 1/ Making `name` required if `filterable` is set in the content\n    schema for this format, and making sure thats enforced, so we\n    can catch this early in CI\n 2/ Simplfying the facet parameters to try and avoid some of the\n    naming confusion, eg, requiring `name`, and using it for\n    `short_name` or `preposition` if they're not explicitly set.","distinct":false,"url":"https://api.github.com/repos/alphagov/policy-publisher/commits/322bb263f56435bb229b9954a676c35d276de20c"},{"sha":"5ade0c775e4275129dbcf73c9bd33d610f06b883","author":{"email":"58e6b3a414a1e090dfc6029add0f3555ccba127f@e26.co.uk","name":"Edd Sowden"},"message":"Merge pull request #82 from alphagov/set-facet-filter-names\n\nSet name fields for filtered facets","distinct":false,"url":"https://api.github.com/repos/alphagov/policy-publisher/commits/5ade0c775e4275129dbcf73c9bd33d610f06b883"}]}