{"action":"closed","issue":{"url":"https://api.github.com/repos/GoogleChrome/sw-helpers/issues/48","repository_url":"https://api.github.com/repos/GoogleChrome/sw-helpers","labels_url":"https://api.github.com/repos/GoogleChrome/sw-helpers/issues/48/labels{/name}","comments_url":"https://api.github.com/repos/GoogleChrome/sw-helpers/issues/48/comments","events_url":"https://api.github.com/repos/GoogleChrome/sw-helpers/issues/48/events","html_url":"https://github.com/GoogleChrome/sw-helpers/issues/48","id":183741698,"number":48,"title":"Improve project health [meta bug]","user":{"login":"addyosmani","id":110953,"avatar_url":"https://avatars.githubusercontent.com/u/110953?v=3","gravatar_id":"","url":"https://api.github.com/users/addyosmani","html_url":"https://github.com/addyosmani","followers_url":"https://api.github.com/users/addyosmani/followers","following_url":"https://api.github.com/users/addyosmani/following{/other_user}","gists_url":"https://api.github.com/users/addyosmani/gists{/gist_id}","starred_url":"https://api.github.com/users/addyosmani/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/addyosmani/subscriptions","organizations_url":"https://api.github.com/users/addyosmani/orgs","repos_url":"https://api.github.com/users/addyosmani/repos","events_url":"https://api.github.com/users/addyosmani/events{/privacy}","received_events_url":"https://api.github.com/users/addyosmani/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-10-18T16:44:44Z","updated_at":"2016-12-09T22:39:47Z","closed_at":"2016-12-09T22:39:47Z","body":"There are a number of project health improvements we could make to the current setup:\r\n- [x] **[Make the failing tests pass](https://github.com/GoogleChrome/sw-helpers/issues/50)** - it's harder to understand the impact of new changes (and existing issues) with sub-projects when the tests have been failing for a while. Let's see if we can get them passing again before adding in new work. Right now it's hard to understand when the tests last actually went green (maybe [3 months ago](https://travis-ci.org/GoogleChrome/sw-helpers/builds/147627696)? :))\r\n- [x] **[Consider scoping tests to supported browsers](https://github.com/GoogleChrome/sw-helpers/issues/51)** - when running `--project=sw-offline-google-analytics` I see a lot of tests failing in Safari (which doesn't support Service Worker). Selenium assistant can find any and all browsers available, we just need to check them against a browserId.\r\n- [x] **Provide more insight into build health per project** - I believe we currently only display a single build status for our CI for the overall repo. I'd like to suggest we also include badges for individual projects in the README so folks can instantly tell what is green and what is not.\r\n- [x] **[Decide on build artifacts](https://github.com/GoogleChrome/sw-helpers/issues/52)** - users have asked for us to consider including minified builds in our npm packages (#31). It would be good to decide on this so we can consistently apply it across the subprojects.\r\n- [x] **Get linting to pass** - This has [just](https://github.com/GoogleChrome/sw-helpers/pull/46) been done as part of the work on docs. \r\n"}}
{"actor":{"display_login":"gauntface"}}