fix: Fixed the bug that the Zig version jumps, and now fmt is not

required

Author: justpav05

.github/PULL_REQUEST_TEMPLATE.md

@@ -8,4 +8,4 @@
       a `REUSE.toml` annotation if a header doesn't fit the file format
 - [ ] `reuse lint` passes
 - [ ] `zig build test -Doptimize=ReleaseSafe` passes
-- [ ] `zig fmt --check .` is clean
+- [ ] `zig fmt .` applied (CI's formatting check is currently non-blocking, see `CONTRIBUTING.md`)

.github/workflows/ci-zig.yml

@@ -19,6 +19,11 @@ jobs:
   fmt:
     name: Formatting
     runs-on: ubuntu-latest
+    # Non-blocking for now: this repo tracks Zig master, and `zig fmt`'s output shifts between
+    # nightly builds, so a contributor's locally-installed Zig can disagree with whatever CI
+    # happens to resolve `master` to on a given day. Drop `continue-on-error` once local/CI
+    # toolchains are pinned to the same version (see CONTRIBUTING.md).
+    continue-on-error: true
     steps:
       - uses: actions/checkout@v4
 

CONTRIBUTING.md

@@ -63,5 +63,9 @@ license of the directory the file lives in. Run `reuse lint` before submitting;
 
 ## Pull requests
 
-Keep PRs scoped to one change. Make sure `zig build test -Doptimize=ReleaseSafe`, `zig fmt --check
-.`, and `reuse lint` all pass before opening — see the PR template's checklist.
+Keep PRs scoped to one change. Make sure `zig build test -Doptimize=ReleaseSafe` and `reuse lint`
+both pass before opening — see the PR template's checklist. Run `zig fmt .` too, but note that CI's
+formatting check is currently non-blocking (`continue-on-error`): this repo tracks Zig master, and
+`zig fmt`'s output can disagree between your locally-installed Zig and whatever nightly CI resolves
+`master` to on a given day. See the `fmt` job in `.github/workflows/ci-zig.yml` for the exact
+reasoning and when to turn the gate back on.