Add "Run on InfiniEmu" link to pull requests, update actions/upload-artifact

[pipe01]

Using nightly.link and corsproxy.io we can generate a link that, when clicked, will direct users to a build of the latest commit of a pull request running on InfiniEmu.

It's also worth noting that GitHub actions artifacts expire after 90 days.

[github-actions]

Build size and comparison to main:

Section	Size	Difference
text	374512B	-16B
data	948B	0B
bss	63488B	0B

Run in InfiniEmu

[liamcharger]

Would really like to see this merged, this makes testing PRs much easier!

[FintasticMan]

Love it!

[mark9064]

Is using an open CORS proxy wise? It feels dangerous to trust it with user traffic - if it started acting maliciously (got hacked, owner decided to cash in etc) it could return whatever it wanted to user's browsers

[pipe01]

Maybe not, but the worst that could happen is that they serve either an invalid ZIP file which would fail to load, or they could serve a different firmware file which would just be annoying.

[mark9064]

I'm trying to think if there's another way to load it, could InfiniEmu itself fetch the firmware somehow?

[pipe01]

If you mean fetching from GitHub directly it's not really possible because there's no official way to download artifacts without being logged in or using an API key, both of which aren't really feasible in this case. That's what nightly.link solves, however it unfortunately doesn't allow CORS.

[mark9064]

Hmm, could the InfiniEmu server fetch it and serve the artefact to the user?

[pipe01]

There's no server per se right now, it's hosted on GitHub pages.

I've made a slight improvement by not hardcoding the CORS proxy into the URL in the comment and instead letting InfiniEmu handle that so that it's easier to change in the future if needed.

[mark9064]

👍 makes sense
Excuse my ignorance, but would requiring being logged in to github remove the need for the proxy? Since anyone who's going to comment on the PR has to be logged in anyway, I don't think it would be an issue

[pipe01]

(Un)fortunately you can't do that because that would mean that you could send any requests on behalf of the logged in user from a different webpage, which is obviously not great.

[mark9064]

Ah, I thought the github cookies for that might be allowed to be samesite, but I guess it makes sense that they're not and there'd have to be a full Oauth flow (which isn't possible on GH pages I guess)