{"push_id":2373196376,"size":2,"distinct_size":1,"ref":"refs/heads/bw/develop","head":"f2c1bc962de0ba3a458769b07b9075367b35d0e7","before":"8336bc67df23a53ab2054d26aeb8d2123d67bbdc","commits":[{"sha":"0e1e3653c64112bdd129a10fb437735fc71aeaf8","author":{"name":"Charlotte Koch","email":"a7ac56a3cdf4c7a76f9d1f120631e76777a90bc7@bowerswilkins.com"},"message":"Remove the Hulafile for now.\n\nThe Hulafile for this repo specifies that not only are the SSH daemon and\nrelated tools installed, but also a some of private keys.\n\nThe Hulafile refers to these keys by means of the Hula file() directive. But\nwhen I imported the Hulafile from hula-pkgs/collection, I didn't\nadditionally import the keys to this repo, too.  Consequently, the build\nfails because it's trying to install files which don't exist.\n\nThe naive solution would be to copy the keys to this repo, but that will be\npatently bad because they are private SSH keys that only B&W engineers ought\nto have access to.\n\nThe way that we have been protecting those keys is by leveraging the fact\nthat hula-pkgs/collection *is* a private/protected space.\n\nSo the change here is to revert to that old behavior for now. Don't break\nthe build AND make sure the keys remain secret.","distinct":false,"url":"https://api.github.com/repos/bw-oss/dropbear/commits/0e1e3653c64112bdd129a10fb437735fc71aeaf8"},{"sha":"f2c1bc962de0ba3a458769b07b9075367b35d0e7","author":{"name":"Charlotte Koch","email":"eee486e73ea4076cf7f8dfa9edf10c331bf9e884@gmail.com"},"message":"Merge pull request #1 from bw-oss/rm_hulafile_for_now\n\nRemove the Hulafile for now.","distinct":true,"url":"https://api.github.com/repos/bw-oss/dropbear/commits/f2c1bc962de0ba3a458769b07b9075367b35d0e7"}]}
{"actor":{"display_login":"dressupgeekout"}}