Integrate BrowserView editor with GitHub's Personal Token & API

[BigBlueHat]

It's possible, though very "geeky", to setup a personal access token and use that with JS to make changes to GitHub repos. It would be handy if there's interest/need to provide more than copy/paste "API" for getting content onto GitHub.

Copy/paste is far more widely supported, though. 😉

Idea presented in #64 (comment) fwiw.

[iherman]

It is certainly a possible future plans if there is a need for it. Personally, though it is there, I have never used it in my own 'workflow' on handling minutes: the repo is cloned on my disk.

What I am not sure of is how to store personal access token in the local store. Storing it in clear text does not seem to be a good idea, so it needs some more sophisticated tools.

[BigBlueHat]

@iherman yeah. I'd not store it. You'd have to add it (like a password) each time. We can link to the screen where folks can retrieve it (which requires them to be logged in to GitHub of course), they can copy/paste that, and then use it for auth.

It doesn't (in browser or on command line) match my current workflow either, though...so maybe we should just close as "wontfix" and save it for a rainy day? 😉

FWIW, I prefer to add scribejs as a dev dependency, and then script it into my use of locally checked out repos--see this JSON-LD WG example usage.

Cool to close as "wontfix" (or should we add a "someday-maybe" tag? 😁

[iherman]

A have created a "maybe one day..." label, and I have added this label to this issue 😄

[BigBlueHat]

Love the new label. Closing this until we find a rainy day. 🌧