{"action":"closed","issue":{"url":"https://api.github.com/repos/janinko/ghprb/issues/215","labels_url":"https://api.github.com/repos/janinko/ghprb/issues/215/labels{/name}","comments_url":"https://api.github.com/repos/janinko/ghprb/issues/215/comments","events_url":"https://api.github.com/repos/janinko/ghprb/issues/215/events","html_url":"https://github.com/janinko/ghprb/issues/215","id":53772985,"number":215,"title":"trigger phrases do not work if issued by the user who owns API key","user":{"login":"skrobul","id":183976,"avatar_url":"https://avatars.githubusercontent.com/u/183976?v=3","gravatar_id":"","url":"https://api.github.com/users/skrobul","html_url":"https://github.com/skrobul","followers_url":"https://api.github.com/users/skrobul/followers","following_url":"https://api.github.com/users/skrobul/following{/other_user}","gists_url":"https://api.github.com/users/skrobul/gists{/gist_id}","starred_url":"https://api.github.com/users/skrobul/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/skrobul/subscriptions","organizations_url":"https://api.github.com/users/skrobul/orgs","repos_url":"https://api.github.com/users/skrobul/repos","events_url":"https://api.github.com/users/skrobul/events{/privacy}","received_events_url":"https://api.github.com/users/skrobul/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-01-08T16:54:03Z","updated_at":"2015-01-20T04:18:10Z","closed_at":"2015-01-20T04:18:10Z","body":"This is continuation of closed #188. \r\n\r\nDespite not being best security practice, lot of people use their own Github accounts to generate API tokens. This is often due to limited number of accounts that organizations can create on GHE (licensing restrictions, etc). In my personal example, I used my own account to generate token for jenkins and it worked well for long time. \r\n\r\nRecently, I have updated GHPRB to newest release and it suddenly stopped working. After short investigation, it turns out that 1fd29de introduced breaking change by ignoring all comments from the bot user, therefore on-demand builds stopped working completely and to my knowledge there is no sensible workaround. Closing and re-opening PR is not sensible option.\r\n\r\nFor now, the only workaround I found was downgrading to `1.14-7`."}}