Add fix contribution form

[Noggog]

Might be nice for users to be able to submit a fix via the website.

This will do a few things:

• Associate the fix with a nexus account, or at least allow us to pull some info of who is submitting it
• If they also (Log into Github #2 ), then we can pull info from that.
• Allow for some blurbs on "best practices", and outline the ways users can submit fixes
• If Spriggit ends up being used, then the website would be a portal to intake raw esp files.
  • Have a server run spriggit and initiate a text-based PR for the user
  • We can attach any descriptions/burbs taken from the websites intake forms
  • if Github is logged in, or the github email provided, then maybe the PR can add that as an additional author? (Would have to research how those additional author systems work)

Overall, would help a lot with accepting fixes from people intimidated by actually interacting with Git, or people that just want to work with raw esps on their side

[Pickysaurus]

I've found a possible means to store files submitted via the site - https://vercel.com/docs/storage/vercel-blob

I'd have to learn how to set it up properly though.

[Noggog]

For people cloning Git repos directly, committing, and opening PRs like a developer, this whole issue will be N/A

This issue is mainly for the crowd that is grabbing our new nightly releases:
https://github.com/Starfield-Community-Patch/Starfield-Community-Patch/releases/tag/nightly

This crowd is the one not familiar with using git too much. They go and grab that nightly release as they just want the latest version nice and easy, without dealing with Git, Spriggit, etc.

This same crowd will be ones that also dont want to deal with it on the return trip. Once they have a fix to contribute, they again won't want to deal with Git, Spriggit, etc. I think this issue will be a big step towards filling out the workflow for this crowd.

---

How this might be done:

Prep:

• Make a website input form that takes in some info + the zip file of mod contents (esp, assets, etc)
• Define a github workflow like this https://github.com/dragonjet-labs/sfcp-flows/blob/fix/test8/.github/workflows/spriggit.yaml that knows how to take in the information from the web form (path to the uploaded zip, name of the target git branch to make, maybe some message)
• Make a github account to handle these SCFP official automatic systems

Upload workflow:

• User uses form to initiate. Fills out message, uploads zip, etc.
• Upload that file somewhere (vercel blob?)
• Start the github workflow via the Github API https://stackoverflow.com/a/70154713
• Get PR with the resulting content
• Maybe redirect user to the PR page? (unsure how this would be done, offhand)

---

This would give this style of user an easy way to drop off a fix without dealing (too much) with git.
Only downside might be they won't know how to follow up too well. They will have to get to the PR to have back and forth discussions. Also, we might need to find a way to add followup work. Maybe a similar workflow, but targeting a PR's ID as part of the dialog input?

Anyway, just brainstorming how to get the non-Git folks on board more cleanly