rust_workflow_template

8 Commits

Include renames

Author	SHA1	Message	Date
melfely	77cfc8bed9	ci: added git user and correct cargo repo token signature Release-plz / Release-plz release (push) Successful in 1m33s Details Release-plz / Release-plz PR (push) Successful in 1m34s Details	2026-09-10 20:12:55 -05:00
melfely	a70cbca5a9	ci: Change from release-plz action to cli Release-plz / Release-plz release (push) Failing after 1m47s Details Release-plz / Release-plz PR (push) Failing after 1m54s Details The action currently only supports github (I think) while the CLI tool claims to support gitea (the action also does...)	2026-09-10 20:00:06 -05:00
melfely	bbca93470c	ci: replaces v0.5 with v0.4 (this working is a hell of a stretch) Release-plz / Release-plz PR (push) Failing after 1m20s Details Release-plz / Release-plz release (push) Failing after 1m20s Details	2026-09-10 19:36:18 -05:00
melfely	a1aaf5cd7e	ci: Added gh tool install. Release-plz / Release-plz PR (push) Failing after 1m43s Details Release-plz / Release-plz release (push) Failing after 1m44s Details	2026-09-10 19:31:37 -05:00
melfely	b3d5f4ef18	ci: Removed Github token from the run. Release-plz / Release-plz release (push) Failing after 1m38s Details Release-plz / Release-plz PR (push) Failing after 1m40s Details	2026-09-10 18:54:03 -05:00
melfely	316a3c591d	ci: Added Release-Plz CI workflow. Release-plz / Release-plz release (push) Failing after 1m53s Details Release-plz / Release-plz PR (push) Failing after 1m55s Details	2026-09-10 18:47:25 -05:00
melfely	6d48820a7e	ci: Rename Lint Workflow Lint & Build / Linting (pull_request) Successful in 1m17s Details Lint & Build / Build (pull_request) Successful in 55s Details Lint & Build / Cross-Build-Linux (pull_request) Successful in 2m5s Details Lint & Build / Cross-Build-MacOS (pull_request) Successful in 2m44s Details Lint & Build / Test (pull_request) Successful in 1m17s Details Lint & Build / Cross-Build-Windows (pull_request) Successful in 1m27s Details The name was too long, and looks bad in most of the Gitea UI elements, a shorter name will be much better.	2026-09-10 20:32:06 +00:00
melfely	32d1e2cd29	ci: Added lint.yml which tests for linting and build on multiple platforms Crossplatform Linting && Build / Test (pull_request) Successful in 1m15s Details Crossplatform Linting && Build / Test (push) Successful in 1m31s Details Crossplatform Linting && Build / Cross-Build-Windows (push) Successful in 2m11s Details Crossplatform Linting && Build / Cross-Build-Linux (push) Successful in 2m42s Details Crossplatform Linting && Build / Cross-Build-MacOS (push) Successful in 3m2s Details Crossplatform Linting && Build / Linting (pull_request) Successful in 1m20s Details Crossplatform Linting && Build / Build (pull_request) Successful in 59s Details Crossplatform Linting && Build / Cross-Build-Windows (pull_request) Successful in 1m58s Details Crossplatform Linting && Build / Cross-Build-Linux (pull_request) Successful in 2m30s Details Crossplatform Linting && Build / Cross-Build-MacOS (pull_request) Successful in 2m50s Details Crossplatform Linting && Build / Linting (push) Successful in 1m15s Details Crossplatform Linting && Build / Build (push) Successful in 1m5s Details This uses a 3 step process Lint -> Linux x86 Build -> [Linux x86 Test, Windows x86 Build, MacOS Check, Linux aarch64 Build] The build steps being seperate from the linux build is so that its clear WHICH OS is preventing the build, along with if it doesn't build for linux x86 (MY dev machines) then there is ZERO point in checking other OS since all of my work happens on linux x86. This reduces Runtime on just outright bad pull-requests. Then we have plenty of runners, so we can easily run all 4 of the other jobs in the final step in parallel. The MacOS steps includes a build BUT will pass regardless of its output, because the build step for MacOS is fairly unrelaible, so this relies on a check only. The main difference between a check and a builds is that build calls the linker, while the check does not. Since the linker commonly fails in a cross-compile, while check verifies the rust code itself is techincally compatible with the OS. (IE no dependencies outright do not support the target). Which is a good enough for the most part.	2026-09-10 14:27:13 -05:00