{"action":"created","issue":{"url":"https://api.github.com/repos/timwis/jkan/issues/55","repository_url":"https://api.github.com/repos/timwis/jkan","labels_url":"https://api.github.com/repos/timwis/jkan/issues/55/labels{/name}","comments_url":"https://api.github.com/repos/timwis/jkan/issues/55/comments","events_url":"https://api.github.com/repos/timwis/jkan/issues/55/events","html_url":"https://github.com/timwis/jkan/issues/55","id":144070261,"number":55,"title":"Set up is more complicated than forking","user":{"login":"waldoj","id":656758,"avatar_url":"https://avatars.githubusercontent.com/u/656758?v=3","gravatar_id":"","url":"https://api.github.com/users/waldoj","html_url":"https://github.com/waldoj","followers_url":"https://api.github.com/users/waldoj/followers","following_url":"https://api.github.com/users/waldoj/following{/other_user}","gists_url":"https://api.github.com/users/waldoj/gists{/gist_id}","starred_url":"https://api.github.com/users/waldoj/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/waldoj/subscriptions","organizations_url":"https://api.github.com/users/waldoj/orgs","repos_url":"https://api.github.com/users/waldoj/repos","events_url":"https://api.github.com/users/waldoj/events{/privacy}","received_events_url":"https://api.github.com/users/waldoj/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-03-28T20:07:59Z","updated_at":"2016-03-28T21:33:43Z","closed_at":null,"body":"GitHub doesn't deploy to GitHub Pages after a fork, it turns out—it's necessary to make a commit to that fork first. (This is contra to [the setup instructions](https://jkan.io/#get-started).) Unless there's a way around this, I imagine that the instructions will have to modified to include a step in which the repo is altered in some way, e.g. a dataset is added (which I appreciate isn't yet supported)."},"comment":{"url":"https://api.github.com/repos/timwis/jkan/issues/comments/202588680","html_url":"https://github.com/timwis/jkan/issues/55#issuecomment-202588680","issue_url":"https://api.github.com/repos/timwis/jkan/issues/55","id":202588680,"user":{"login":"timwis","id":761444,"avatar_url":"https://avatars.githubusercontent.com/u/761444?v=3","gravatar_id":"","url":"https://api.github.com/users/timwis","html_url":"https://github.com/timwis","followers_url":"https://api.github.com/users/timwis/followers","following_url":"https://api.github.com/users/timwis/following{/other_user}","gists_url":"https://api.github.com/users/timwis/gists{/gist_id}","starred_url":"https://api.github.com/users/timwis/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/timwis/subscriptions","organizations_url":"https://api.github.com/users/timwis/orgs","repos_url":"https://api.github.com/users/timwis/repos","events_url":"https://api.github.com/users/timwis/events{/privacy}","received_events_url":"https://api.github.com/users/timwis/received_events","type":"User","site_admin":false},"created_at":"2016-03-28T21:33:43Z","updated_at":"2016-03-28T21:33:43Z","body":"Oh no! That's a shame. We can't even rely on the setup page to make a commit because the setup page doesn't exist yet. A couple ideas come to mind:\r\n\r\n1. Have them edit some placebo file using github's interface, like a file called `activate`, and type something in it\r\n2. Take an approach similar to waffle.io or gitter, where we have some bot that sends you a pull request. The bot could be activated when the repo is forked, and send an empty commit that they could then merge. This would require a central \"jkan controlled\" server, but only for ease-of-use purposes\r\n\r\nThanks for catching this, I swore it worked before..."}}