{"push_id":626095330,"size":5,"distinct_size":1,"ref":"refs/heads/master","head":"fa90725098bb2c91c49cc3b9fda3ff34c5d1e92a","before":"b8ef7f6f6fbc62ee31b87c58df566e7de4df8248","commits":[{"sha":"0e7e24f9be19a5c294a3eb035d3ea01e60c4a189","author":{"email":"742d16f32570b1c4e9a798a62cbe09b608f64dd7@gmail.com","name":"Dominic Baggott"},"message":"Stop passing arrays to fill_in_fields helper\n\nWe don't make use of this functionality anywhere, and it's just\nconfusing to have lying around until the point we definitely need it.","distinct":false,"url":"https://api.github.com/repos/alphagov/specialist-publisher/commits/0e7e24f9be19a5c294a3eb035d3ea01e60c4a189"},{"sha":"7d04ebcab699b434becd88f5c3495d88a3ff77b9","author":{"email":"742d16f32570b1c4e9a798a62cbe09b608f64dd7@gmail.com","name":"Dominic Baggott"},"message":"Extract fill_in_field method\n\nMake the existing `fill_in_fields` method responsible only for iterating\nthrough a hash of names and values.","distinct":false,"url":"https://api.github.com/repos/alphagov/specialist-publisher/commits/7d04ebcab699b434becd88f5c3495d88a3ff77b9"},{"sha":"e7a4ea1d6620dd9a7fe6aa61ea9282ae2ad67f78","author":{"email":"742d16f32570b1c4e9a798a62cbe09b608f64dd7@gmail.com","name":"Dominic Baggott"},"message":"Handle select2 fields in fill_in_field helper\n\nWhen a select2 field is initialised it copies the label tag for the\noriginal field, so there are two labels with the same text. That causes\nthe `find_field` helper to raise a `Capybara::Ambiguous` error.\n\nTo work around this, first try to find a select field and if found\nselect the value from that. If there isn't a select field, just use the\n`fill_in` helper and let Capybara work out which field to use.\n\nWhen select2 is involved, this will find the original select field\nbypassing the select2 functionality. Ideally this method would account\nfor select2 fields and interact with them in the same way a user would\n(by clicking to open a dropdown list, then clicking an item). That seems\nlike a piece of yak-shaving too far for now, so this at least keeps\neverything working.","distinct":false,"url":"https://api.github.com/repos/alphagov/specialist-publisher/commits/e7a4ea1d6620dd9a7fe6aa61ea9282ae2ad67f78"},{"sha":"9f409ad7c9f6608086076c492f700aeb0d807191","author":{"email":"742d16f32570b1c4e9a798a62cbe09b608f64dd7@gmail.com","name":"Dominic Baggott"},"message":"Allow multiple market_sector values for CMA cases\n\nSince `market_sector` is required in validations we have to select a\nvalue for it. Previously it was \"just working\" because the field\ndefaulted to the first option in the select.\n\nWe have to update the values we look for since in the interface we're\npicking `\"Energy\"`, but the data we send out is `[\"energy\"]`. The\napproach I've used will only work for single word values -- that's good\nenough for now.","distinct":false,"url":"https://api.github.com/repos/alphagov/specialist-publisher/commits/9f409ad7c9f6608086076c492f700aeb0d807191"},{"sha":"fa90725098bb2c91c49cc3b9fda3ff34c5d1e92a","author":{"email":"c22b5f9178342609428d6f51b2c5af4c0bde6a42@tommyp.org","name":"Tommy Palmer"},"message":"Merge pull request #463 from alphagov/allow-multiple-values-for-cma-case-markets\n\nAllow multiple values for cma case markets","distinct":true,"url":"https://api.github.com/repos/alphagov/specialist-publisher/commits/fa90725098bb2c91c49cc3b9fda3ff34c5d1e92a"}]}