ci: skip the crate gate for website-only changes

Add website/** and the website workflow to ci.yaml's paths-ignore, so a
push confined to the website subproject (built + published by
website.yaml) no longer runs clippy+test. A push that also touches crate
code still gates (paths-ignore skips only when all files match).

.gitea/workflows/ci.yaml

@@ -13,17 +13,23 @@ on:
     # run (the release workflow owns tags). Pushing commits + a tag together
     # still gates the commits via the branch push.
     branches: ['**']
-    # Skip the gate for docs-only changes — markdown can't affect clippy/test.
+    # Skip the gate for changes that can't affect clippy/test — docs, markdown,
-    # A push touching code *and* docs still runs (not all files are ignored).
+    # and the website subproject (it has its own workflow, website.yaml, that
+    # builds + publishes it). A push touching crate code *and* these still runs
+    # (paths-ignore only skips when *all* changed files match).
     # Note: flake/toolchain changes are NOT ignored — they can shift the
     # toolchain and thus lint/test outcomes.
     paths-ignore:
       - 'docs/**'
       - '**/*.md'
+      - 'website/**'
+      - '.gitea/workflows/website.yaml'
   pull_request:
     paths-ignore:
       - 'docs/**'
       - '**/*.md'
+      - 'website/**'
+      - '.gitea/workflows/website.yaml'
 
 jobs:
   gate: