{"action":"created","issue":{"url":"https://api.github.com/repos/brigade/overcommit/issues/389","repository_url":"https://api.github.com/repos/brigade/overcommit","labels_url":"https://api.github.com/repos/brigade/overcommit/issues/389/labels{/name}","comments_url":"https://api.github.com/repos/brigade/overcommit/issues/389/comments","events_url":"https://api.github.com/repos/brigade/overcommit/issues/389/events","html_url":"https://github.com/brigade/overcommit/issues/389","id":161992558,"number":389,"title":"Is it possible to wait until push to run the CommitMsg hook?","user":{"login":"monfresh","id":811150,"avatar_url":"https://avatars.githubusercontent.com/u/811150?v=3","gravatar_id":"","url":"https://api.github.com/users/monfresh","html_url":"https://github.com/monfresh","followers_url":"https://api.github.com/users/monfresh/followers","following_url":"https://api.github.com/users/monfresh/following{/other_user}","gists_url":"https://api.github.com/users/monfresh/gists{/gist_id}","starred_url":"https://api.github.com/users/monfresh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/monfresh/subscriptions","organizations_url":"https://api.github.com/users/monfresh/orgs","repos_url":"https://api.github.com/users/monfresh/repos","events_url":"https://api.github.com/users/monfresh/events{/privacy}","received_events_url":"https://api.github.com/users/monfresh/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/brigade/overcommit/labels/question","name":"question","color":"d4c5f9"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-06-23T18:34:27Z","updated_at":"2016-06-23T19:16:23Z","closed_at":"2016-06-23T19:16:23Z","body":"A typical workflow when working on a branch is to make several commits locally without pushing to GitHub, and once it's ready to be pushed as a pull request, the commits might or might not be squashed. Having overcommit complain about each individual commit interrupts the flow. It would be a much better experience to wait until the commits are actually pushed before checking them.\r\n\r\nIs there a way to configure this behavior?\r\n\r\nThanks!"},"comment":{"url":"https://api.github.com/repos/brigade/overcommit/issues/comments/228155282","html_url":"https://github.com/brigade/overcommit/issues/389#issuecomment-228155282","issue_url":"https://api.github.com/repos/brigade/overcommit/issues/389","id":228155282,"user":{"login":"sds","id":677877,"avatar_url":"https://avatars.githubusercontent.com/u/677877?v=3","gravatar_id":"","url":"https://api.github.com/users/sds","html_url":"https://github.com/sds","followers_url":"https://api.github.com/users/sds/followers","following_url":"https://api.github.com/users/sds/following{/other_user}","gists_url":"https://api.github.com/users/sds/gists{/gist_id}","starred_url":"https://api.github.com/users/sds/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sds/subscriptions","organizations_url":"https://api.github.com/users/sds/orgs","repos_url":"https://api.github.com/users/sds/repos","events_url":"https://api.github.com/users/sds/events{/privacy}","received_events_url":"https://api.github.com/users/sds/received_events","type":"User","site_admin":false},"created_at":"2016-06-23T19:16:23Z","updated_at":"2016-06-23T19:16:23Z","body":"Hey @monfresh,\r\n\r\n`CommitMsg` hooks aren't triggered by Overcommit, but by `git` itself.\r\n\r\nYour potential options/workarounds are:\r\n\r\n- Move your `CommitMsg` hooks to `PrePush` hooks so they only run on push\r\n- Disable `CommitMsg` hooks entirely\r\n\r\nAt the end of the day, creating a `CommitMsg` hook indicates you want the hook to run when `git` runs the `commit-msg` hook. There's no getting around this other than to move your checks into a different hook.\r\n\r\nHope this helps!"}}
{"actor":{"display_login":"sds"}}