{"action":"created","issue":{"url":"https://api.github.com/repos/pelias/pelias/issues/345","repository_url":"https://api.github.com/repos/pelias/pelias","labels_url":"https://api.github.com/repos/pelias/pelias/issues/345/labels{/name}","comments_url":"https://api.github.com/repos/pelias/pelias/issues/345/comments","events_url":"https://api.github.com/repos/pelias/pelias/issues/345/events","html_url":"https://github.com/pelias/pelias/issues/345","id":157346976,"number":345,"title":"Automate more of our pull request/release workflow","user":{"login":"orangejulius","id":111716,"avatar_url":"https://avatars.githubusercontent.com/u/111716?v=3","gravatar_id":"","url":"https://api.github.com/users/orangejulius","html_url":"https://github.com/orangejulius","followers_url":"https://api.github.com/users/orangejulius/followers","following_url":"https://api.github.com/users/orangejulius/following{/other_user}","gists_url":"https://api.github.com/users/orangejulius/gists{/gist_id}","starred_url":"https://api.github.com/users/orangejulius/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/orangejulius/subscriptions","organizations_url":"https://api.github.com/users/orangejulius/orgs","repos_url":"https://api.github.com/users/orangejulius/repos","events_url":"https://api.github.com/users/orangejulius/events{/privacy}","received_events_url":"https://api.github.com/users/orangejulius/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/pelias/pelias/labels/discussion","name":"discussion","color":"fad8c7"},{"url":"https://api.github.com/repos/pelias/pelias/labels/processed","name":"processed","color":"e6e6e6"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2016-05-28T16:45:53Z","updated_at":"2016-06-01T22:12:33Z","closed_at":null,"body":"At EmpireJS @gr2m gave a great talk about [building welcoming open source communities](http://hood.ie/blog/welcoming-communities.html) that probably got several of us thinking! There were many takeaways about general interaction but two specifically regarding automation of workflows I would love to see us implement immediately.\r\n\r\n## Use [semantic-release](https://github.com/semantic-release/semantic-release) to automate NPM releases :airplane: \r\n\r\nNPM releases has been something we've had a bit of discussion about and not always done perfectly. Some cases where things haven't worked great:\r\n\r\n* Just today we had a user report [an issue](pelias/pelias#344) that we had fixed, but we hadn't released the fix in an NPM module yet\r\n* I've accidentally included over 1GB of test data in an NPM release which caused no real harm, but slows everything down and takes up space needlessly\r\n* Sometimes we just waste time trying to decide the right version\r\n\r\nSemantic-release automatically does NPM releases whenever a new commit hits the master branch, on TravisCI, and automatically increments the version correctly based on the rules of [semantic versioning](http://semver.org/)! Commits simply have to be tagged with the appropriate prefix in the commit message to state whether they're bug fixes, new features, or breaking changes. There's apparently also a way to reject merges into master that don't properly tag the commits.\r\n\r\n## Use [LGTM](https://lgtm.co/docs/overview/) to provide simple checks for code review :+1: \r\n\r\nWe are generally really good at doing at least a quick code review before any code is merged, so why not enforce that with a Github check? I'd also love to see us start to invite some of our awesome external contributors to become maintainers of pelias repositories, and having more of our preferred workflow automated will help us as we do that."},"comment":{"url":"https://api.github.com/repos/pelias/pelias/issues/comments/223140863","html_url":"https://github.com/pelias/pelias/issues/345#issuecomment-223140863","issue_url":"https://api.github.com/repos/pelias/pelias/issues/345","id":223140863,"user":{"login":"orangejulius","id":111716,"avatar_url":"https://avatars.githubusercontent.com/u/111716?v=3","gravatar_id":"","url":"https://api.github.com/users/orangejulius","html_url":"https://github.com/orangejulius","followers_url":"https://api.github.com/users/orangejulius/followers","following_url":"https://api.github.com/users/orangejulius/following{/other_user}","gists_url":"https://api.github.com/users/orangejulius/gists{/gist_id}","starred_url":"https://api.github.com/users/orangejulius/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/orangejulius/subscriptions","organizations_url":"https://api.github.com/users/orangejulius/orgs","repos_url":"https://api.github.com/users/orangejulius/repos","events_url":"https://api.github.com/users/orangejulius/events{/privacy}","received_events_url":"https://api.github.com/users/orangejulius/received_events","type":"User","site_admin":false},"created_at":"2016-06-01T22:12:33Z","updated_at":"2016-06-01T22:12:33Z","body":"Oh, one more cool thing. We should add test coverage badges to our repos via Coveralls. The output in [Travis](https://travis-ci.org/hoodiehq/hoodie/builds/133007324) is quite nice, the [setup](https://github.com/hoodiehq/hoodie/blob/master/package.json#L74) is not hard at all."}}
{"actor":{"display_login":"orangejulius"}}