{"action":"closed","issue":{"url":"https://api.github.com/repos/jorisroovers/gitlint/issues/19","repository_url":"https://api.github.com/repos/jorisroovers/gitlint","labels_url":"https://api.github.com/repos/jorisroovers/gitlint/issues/19/labels{/name}","comments_url":"https://api.github.com/repos/jorisroovers/gitlint/issues/19/comments","events_url":"https://api.github.com/repos/jorisroovers/gitlint/issues/19/events","html_url":"https://github.com/jorisroovers/gitlint/issues/19","id":194873057,"number":19,"title":"server-side support?","user":{"login":"aspiers","id":100738,"avatar_url":"https://avatars.githubusercontent.com/u/100738?v=3","gravatar_id":"","url":"https://api.github.com/users/aspiers","html_url":"https://github.com/aspiers","followers_url":"https://api.github.com/users/aspiers/followers","following_url":"https://api.github.com/users/aspiers/following{/other_user}","gists_url":"https://api.github.com/users/aspiers/gists{/gist_id}","starred_url":"https://api.github.com/users/aspiers/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aspiers/subscriptions","organizations_url":"https://api.github.com/users/aspiers/orgs","repos_url":"https://api.github.com/users/aspiers/repos","events_url":"https://api.github.com/users/aspiers/events{/privacy}","received_events_url":"https://api.github.com/users/aspiers/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-12-12T01:28:07Z","updated_at":"2016-12-13T00:53:45Z","closed_at":"2016-12-13T00:53:45Z","body":"It's great having client-side validation, but let's face it some developers will simply forget or be too lazy to set it up, and then they'll submit bad commits for review regardless.  So ideally there should be a way to enforce validation server-side.  Of course the implementation depends on the server in question, but GitHub might be a good place to start.  For example might it be possible to create a GitHub third-party service which runs gitlint server-side whenever a PR is submitted / updated, and then updates a status check on the PR accordingly?\r\n\r\nSee also [codeclimate/spec#45 (allow analysis of commit messages)](https://github.com/codeclimate/spec/issues/45)"}}
{"actor":{"display_login":"aspiers"}}