{"action":"opened","issue":{"url":"https://api.github.com/repos/dspinellis/git-issue/issues/27","repository_url":"https://api.github.com/repos/dspinellis/git-issue","labels_url":"https://api.github.com/repos/dspinellis/git-issue/issues/27/labels{/name}","comments_url":"https://api.github.com/repos/dspinellis/git-issue/issues/27/comments","events_url":"https://api.github.com/repos/dspinellis/git-issue/issues/27/events","html_url":"https://github.com/dspinellis/git-issue/issues/27","id":316320900,"number":27,"title":"import from github/gitlab issues","user":{"login":"r2evans","id":5815808,"avatar_url":"https://avatars0.githubusercontent.com/u/5815808?v=4","gravatar_id":"","url":"https://api.github.com/users/r2evans","html_url":"https://github.com/r2evans","followers_url":"https://api.github.com/users/r2evans/followers","following_url":"https://api.github.com/users/r2evans/following{/other_user}","gists_url":"https://api.github.com/users/r2evans/gists{/gist_id}","starred_url":"https://api.github.com/users/r2evans/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/r2evans/subscriptions","organizations_url":"https://api.github.com/users/r2evans/orgs","repos_url":"https://api.github.com/users/r2evans/repos","events_url":"https://api.github.com/users/r2evans/events{/privacy}","received_events_url":"https://api.github.com/users/r2evans/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-04-20T15:51:54Z","updated_at":"2018-04-20T15:51:54Z","closed_at":null,"author_association":"NONE","body":"In concert with (but not necessarily wholly dependent on) #7, what are your thoughts to a form of connection using [github webhooks](https://developer.github.com/webhooks/) and/or [gitlab api](https://docs.gitlab.com/ce/api/issues.html)?\r\n\r\nFor instance, imagine a webhook or helper script that syncs all current GH/GL issues with the current git-issues project, whether standalone or in the special branch suggested in [my comment in #7](https://github.com/dspinellis/git-issue/issues/9#issuecomment-383133703).\r\n\r\n**Use-case:** I travel often, and I'm either too cheap to buy on-plane internet access or it is unreliable. I'd like to be able to have a solid listing of my issues with comments and supporting artifacts. My current method is to go through each issue and print to a PDF, which is both cumbersome and prone to print-layout artifacts. (And the supporting artifacts are not necessarily attached.)\r\n\r\nI see this potentially being done one or two ways:\r\n\r\n- manually with `git issue import`; the remote url could easily be saved/cached, similar to `git remote`; there would need to be internal differentiation between GH and GL.\r\n\r\n    ```\r\n    git issue import git@github.com:r2evans/myproj\r\n    # optionally but not strictly necessary\r\n    git push origin issues:issues\r\n    ```\r\n\r\n- programmatically, where the GH/GL-hosted project has a trigger script (webhook or CI yml script) that automatically updates the `issues` branch when an issues is created/modified.\r\n\r\n    ```\r\n    git pull origin issues:issues\r\n    ```\r\n\r\nThoughts?"}}
{"actor":{"display_login":"r2evans"}}