update branch name

Author: DoubleStyx

.github/workflows/ci.yml

@@ -3,7 +3,7 @@ name: CI
 
 "on":
   push:
-    branches: [owner, main, master]
+    branches: [master]
     paths:
       - ".github/workflows/ci.yml"
       - ".taplo.toml"

.github/workflows/release.yml

@@ -1,6 +1,6 @@
 # Nightly release pipeline.
 #
-# Picks the newest owner commit that has passed `ci.yml`, builds platform
+# Picks the newest master commit that has passed `ci.yml`, builds platform
 # binaries in release mode, and publishes a GitHub Release with per-platform
 # zips. The most recent release acts as the "last good version" pointer - this
 # workflow no-ops when no new green commit has appeared since.
@@ -34,24 +34,24 @@ jobs:
       tag: ${{ steps.pick.outputs.tag }}
       should_release: ${{ steps.pick.outputs.should_release }}
     steps:
-      - name: Find newest green commit on owner
+      - name: Find newest green commit on master
         id: pick
         env:
           GH_TOKEN: ${{ github.token }}
           FORCE: ${{ inputs.force }}
         run: |
           set -euo pipefail
 
-          # Newest SHA from recent successful CI runs on owner.
+          # Newest SHA from recent successful CI runs on master.
           candidate=$(
             gh api -X GET \
               "repos/${GITHUB_REPOSITORY}/actions/workflows/ci.yml/runs" \
-              -f branch=owner -f status=success -F per_page=100 \
+              -f branch=master -f status=success -F per_page=100 \
               | jq -r '[.workflow_runs | sort_by(.created_at) | reverse | .[].head_sha][0] // ""'
           )
 
           if [ -z "$candidate" ]; then
-            echo "No owner commit has CI green; skipping." | tee -a "$GITHUB_STEP_SUMMARY"
+            echo "No master commit has CI green; skipping." | tee -a "$GITHUB_STEP_SUMMARY"
             echo "should_release=false" >>"$GITHUB_OUTPUT"
             exit 0
           fi

.github/workflows/static.yml

@@ -4,7 +4,7 @@ name: Deploy static content to Pages
 on:
   # Runs on pushes targeting the default branch
   push:
-    branches: ["owner"]
+    branches: ["master"]
     paths:
       - ".github/workflows/static.yml"
       - "index.html"

CONTRIBUTING.md

@@ -278,9 +278,9 @@ The main check workflow lives under `.github/workflows/`.
 
 - `ci.yml` builds and tests the Rust workspace and the .NET solution as independent jobs, each with Ubuntu, Windows, and macOS matrix entries so the Rust and .NET checks can run in parallel. Linux is the only Rust matrix entry that uses `--all-features`, because GStreamer dev packages are reliably installable from the system package manager only on Linux. Windows and macOS still build the `tracy` feature so it stays warning-free on those platforms. The Linux Rust job also installs Vulkan tooling so the `materials::registry` smoke test can find an adapter. The .NET job runs the generator's unit and roundtrip tests, and verifies formatting on Linux only (Windows checkouts can disagree with the in-repo encoding because of `core.autocrlf`, so format checks would fail spuriously there).
 
-The CI workflow triggers on push to `owner`, `main`, or `master`, on pull requests, and on manual dispatch.
+The CI workflow triggers on push to `master`, on pull requests, and on manual dispatch.
 
-Local hooks catch failures before a push, but they are not the final gate because any git hook can be bypassed with `--no-verify`. Protect `owner` with a GitHub branch protection rule or ruleset that requires pull requests and these status checks before merge:
+Local hooks catch failures before a push, but they are not the final gate because any git hook can be bypassed with `--no-verify`. Protect `master` with a GitHub branch protection rule or ruleset that requires pull requests and these status checks before merge:
 
 - `Rust / ubuntu-latest`
 - `Rust / windows-latest`
@@ -289,7 +289,7 @@ Local hooks catch failures before a push, but they are not the final gate becaus
 - `.NET / windows-latest`
 - `.NET / macos-latest`
 
-Block force pushes and branch deletion on `owner` so the hosted CI result remains the authoritative merge gate.
+Block force pushes and branch deletion on `master` so the hosted CI result remains the authoritative merge gate.
 
 ---