payload: {"action":"opened","issue":{"url":"https://api.github.com/repos/deity-io/falcon/issues/749","repository_url":"https://api.github.com/repos/deity-io/falcon","labels_url":"https://api.github.com/repos/deity-io/falcon/issues/749/labels{/name}","comments_url":"https://api.github.com/repos/deity-io/falcon/issues/749/comments","events_url":"https://api.github.com/repos/deity-io/falcon/issues/749/events","html_url":"https://github.com/deity-io/falcon/issues/749","id":536279437,"node_id":"MDU6SXNzdWU1MzYyNzk0Mzc=","number":749,"title":"nextLocation is not accepted when SignIn","user":{"login":"tutok","id":1831641,"node_id":"MDQ6VXNlcjE4MzE2NDE=","avatar_url":"https://avatars0.githubusercontent.com/u/1831641?v=4","gravatar_id":"","url":"https://api.github.com/users/tutok","html_url":"https://github.com/tutok","followers_url":"https://api.github.com/users/tutok/followers","following_url":"https://api.github.com/users/tutok/following{/other_user}","gists_url":"https://api.github.com/users/tutok/gists{/gist_id}","starred_url":"https://api.github.com/users/tutok/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tutok/subscriptions","organizations_url":"https://api.github.com/users/tutok/orgs","repos_url":"https://api.github.com/users/tutok/repos","events_url":"https://api.github.com/users/tutok/events{/privacy}","received_events_url":"https://api.github.com/users/tutok/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2019-12-11T10:28:49Z","updated_at":"2019-12-11T10:28:49Z","closed_at":null,"author_association":"MEMBER","body":"**Describe the bug**\r\n\r\nI do not have an idea when `next` query param appeared on redirect links, but from the very beginning, we have had` nextLocation` passed via `location.state` in order to have clean URLs in the browser.\r\n\r\nPersonally I can not see any reason why we would need `next` query string param (If someone will refresh the page on the sign-in then I think it is ok to redirect him to default `/` page) and I would leave only `location.state.nextLocation`. But if you do not agree then at least we should not brake previously behavior.\r\n\r\n**Expected behavior**\r\nuser should be redirected after sign-in into `location.state.nextLocation` location\r\n\r\n**Additional context**\r\nI found this issue: https://github.com/deity-io/falcon/issues/673\r\n"}}
other: {"actor":{"display_login":"tutok"}}