ci: Initial workflow

[tuxuser]

This adds a basic CI workflow to build the extension via github actions.
It does not implement auto-release on git-tag, so you can still validate the built artifact before actually drafting a release.

Hope this eases the pain of constantly updating the extension ;)

[zeroKilo]

To be honest I dont know how to use this, I dont really trust with "secrets.GITHUB_TOKEN" in there and I dont like to add stuff that I dont understand. Also making these releases is a mess each time, because something breaks on each ghidra release, so I need to manually fix it

[tuxuser]

IMHO

About this CI workflow in general: It should not require any additional work for you, other than bumping the ghidra version once you drafted a new version of the extension.

https://github.com/tuxuser/XEXLoaderWV/blob/2c2d036114cd82632564918c1d6942feb5e64407/.github/workflows/build.yml#L10-L13

Benefit:

• Github will verify it builds fine with the files pushed to the repo
• Contributors can make changes and have the CI verify them too, gives some level of confidence in the own changes and also to you, when reviewing contributions.

---

I dont really trust with "secrets.GITHUB_TOKEN" in there and I dont like to add stuff that I dont understand.

Fair! in this case, secrets.GITHUB_TOKEN is an optional argument to ensure not getting rate-limited when executionng multiple internal github requests in a short timeframe, when fetching the ghidra tarball.

By default, github workflows execute in a read-only context on your github repository. More invasive permissions need to be granted explicitly (like writing comments, pushing stuff etc.) (see https://docs.github.com/en/actions/tutorials/authenticate-with-github_token#granting-additional-permissions)