{"action":"created","issue":{"url":"https://api.github.com/repos/ncase/ncase.github.io/issues/2","repository_url":"https://api.github.com/repos/ncase/ncase.github.io","labels_url":"https://api.github.com/repos/ncase/ncase.github.io/issues/2/labels{/name}","comments_url":"https://api.github.com/repos/ncase/ncase.github.io/issues/2/comments","events_url":"https://api.github.com/repos/ncase/ncase.github.io/issues/2/events","html_url":"https://github.com/ncase/ncase.github.io/issues/2","id":319268934,"number":2,"title":"https?","user":{"login":"ChALkeR","id":291301,"avatar_url":"https://avatars2.githubusercontent.com/u/291301?v=4","gravatar_id":"","url":"https://api.github.com/users/ChALkeR","html_url":"https://github.com/ChALkeR","followers_url":"https://api.github.com/users/ChALkeR/followers","following_url":"https://api.github.com/users/ChALkeR/following{/other_user}","gists_url":"https://api.github.com/users/ChALkeR/gists{/gist_id}","starred_url":"https://api.github.com/users/ChALkeR/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ChALkeR/subscriptions","organizations_url":"https://api.github.com/users/ChALkeR/orgs","repos_url":"https://api.github.com/users/ChALkeR/repos","events_url":"https://api.github.com/users/ChALkeR/events{/privacy}","received_events_url":"https://api.github.com/users/ChALkeR/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-05-01T17:41:07Z","updated_at":"2018-05-01T18:56:35Z","closed_at":null,"author_association":"NONE","body":"Should be easy to do.\r\n\r\nRefs:\r\n* https://blog.github.com/2018-05-01-github-pages-custom-domains-https/ \r\n* https://help.github.com/articles/troubleshooting-custom-domains/#https-errors\r\n* https://help.github.com/articles/securing-your-github-pages-site-with-https/\r\n* https://help.github.com/articles/using-a-custom-domain-with-github-pages/\r\n\r\nBasically, all you need to do is update the A records to the ones mentioned in the second link (the same as the ones for `ncase.github.io`) or just use a CNAME record, and enable «Enforce HTTPS» in repo settings (if such a setting is present). \r\n\r\nAtm, accessing https://ncase.me results in `ERR_CERT_COMMON_NAME_INVALID` error.\r\nAnd that's what some people try to use, e.g. with EFF HTTPS Everywhere addon enabled."},"comment":{"url":"https://api.github.com/repos/ncase/ncase.github.io/issues/comments/385756912","html_url":"https://github.com/ncase/ncase.github.io/issues/2#issuecomment-385756912","issue_url":"https://api.github.com/repos/ncase/ncase.github.io/issues/2","id":385756912,"user":{"login":"ncase","id":825858,"avatar_url":"https://avatars0.githubusercontent.com/u/825858?v=4","gravatar_id":"","url":"https://api.github.com/users/ncase","html_url":"https://github.com/ncase","followers_url":"https://api.github.com/users/ncase/followers","following_url":"https://api.github.com/users/ncase/following{/other_user}","gists_url":"https://api.github.com/users/ncase/gists{/gist_id}","starred_url":"https://api.github.com/users/ncase/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ncase/subscriptions","organizations_url":"https://api.github.com/users/ncase/orgs","repos_url":"https://api.github.com/users/ncase/repos","events_url":"https://api.github.com/users/ncase/events{/privacy}","received_events_url":"https://api.github.com/users/ncase/received_events","type":"User","site_admin":false},"created_at":"2018-05-01T18:56:35Z","updated_at":"2018-05-01T18:56:35Z","author_association":"OWNER","body":"Oh that's amazing!  I was disappointed when I first found out Github Custom Domains couldn't do HTTPS, so this is especially happy news for me :) I'll implement it in the next couple weeks! (trying to take a work-break for a bit after just launching a big project)"}}
{"actor":{"display_login":"ncase"}}