GitHub browser login, create PR automatically

[kmturley]

Currently users fill out the form and then have to login to GitHub to open an issue with the package metadata. Afterwards the issue has to be reviewed and a PR opened manually.

These steps could be skipped by adding the GitHub client browser login to the site frontend:
https://github.com/octokit/octokit.js

Then use the GitHub API to submit a pull request to Open Audio Stack Registry from the site form frontend.

[RustoMCSpit]

Also, we discussed uploading and storing presets.

Presets (and soon MIDI) will be encoded clientside into base64 binary (as a data:URL) which would be placed inside the URL field in the metadata. No images or audio will be stored for presets or MIDI (MIDI would not need audio as there plenty of JS MIDI player modules anyways). Only those two types will be accepted for this as they are small, do not receive updates often, and the users are less technically inclined. The user would go to the OAS site, submit the metadata and file which will only be accepted if it less than 500kb, and then they will click on submit to Github. If the user has an account, it will submit under their own user. If not, a robot will do it. OAS team manually checks file, it good, Github accounts will process it

[kmturley]

This feature would allow:

1. Login to GitHub in the browser window
2. In the background - Fork the Open Audio Stack repository
3. Create a new branch in the fork for the form plugin
4. Upload files to the branch
   • package metadata yaml
   • image preview jpg
   • audio preview flac
   • package files
5. Open a pull request from fork → upstream

In theory this could work for any package type, Plugin, Preset, Project.

Presets (and soon MIDI) will be encoded clientside into base64 binary (as a data:URL) which would be placed inside the URL field in the metadata.

This won't be needed as the file will be uploaded directly to a branch

No images or audio will be stored for presets or MIDI (MIDI would not need audio as there plenty of JS MIDI player modules anyways).

These are still required files for now

file which will only be accepted if it less than 500kb

I don't think we need to limit the filesize here, it can be reviewed as part of the pull request.

it will submit under their own user. If not, a robot will do it.

For this to work it would require server-side code, and the service could be spammed with bad files and bad pull requests. I'd rather advoid this and rely on real GitHub user accounts.