Document (and provide a reference implementation of a web app) on how issue refs can be created and updated centrally via GitHub web hooks.

This workflow provides a single source of truth of issue refs for a team of people all working on the same repo and sharing the same issues. Refs can be cloned directly without having to go through GitHub's API. In addition it is much less likely that updates to issues will be missed by infrequent syncs (we would only miss updates if the web app goes down).

Pull down issue comments as well during the sync process.

(Can we distinguish between issue comments, pull request comments, and line-number comments?)

We'll need to parse the JSON to see open/closed, milestone, and labels.

We can output the JSON in bulk and jq is plenty fast so perhaps we can do this on the fly. If that isn't fast enough we'll have to maintain an index (probably another Git note) for each type.

Initial work in 85cb699. Store that in a ref. Make _process_response a pure function so it can be reused here.

GitHub doesn't return a links header if there is only one page of issues. _get_issues_urls() must take into account a possible missing links header.

Most of the HTTP-level functionality here has been folded into ok.sh and in a generally better way. This lib should just focus on reading/writing issues to the local Git database.

Either dep on ok.sh or pull it in wholesale.

get_issues_urls() must check for a 200 response before continuing.

Add info to the README & site on how to push downloaded issue refs to a remote and why you might want to do that. (Hint: so people can clone them and have limited access to local GitHub issues even without the plugin installed.)

It currently only handles the [email protected]:saltstack/salt.git format.

Open EDITOR to collect the issue title and body then send those via the API to create a new issue. Automatically run sync after that to store a local copy.