From 50ab15cbe9c400fc6bd063c3f9c154cc657a2c70 Mon Sep 17 00:00:00 2001 From: Claude Date: Mon, 9 Nov 2026 19:59:50 -0500 Subject: [PATCH] Add Gitea CI so upstream's GitHub workflows stop running Gitea only falls back to .github/workflows when a commit has no .gitea/workflows. Adding a small Linux-only workflow here stops upstream OpenMW's macOS, Windows and full Ubuntu workflows from queueing on the shared runner, without editing upstream's files. The workflow checks the Docker build scripts on pushes to main that touch docker/ or the workflow itself, with a concurrency group and a 10-minute timeout. ASHLAR.md notes that refs without .gitea/workflows, such as upstream tags, still fall back to .github. Refs DevOps/software-infrastructure#34 Co-Authored-By: Claude Opus 5.5 --- .gitea/workflows/ashlar-checks.yaml | 50 +++++++++++++++++++++++++++++ ASHLAR.md | 10 +++++- 2 files changed, 59 insertions(+), 1 deletion(-) create mode 100644 .gitea/workflows/ashlar-checks.yaml diff --git a/.gitea/workflows/ashlar-checks.yaml b/.gitea/workflows/ashlar-checks.yaml new file mode 100644 index 0000000000..7e204cbbf4 --- /dev/null +++ b/.gitea/workflows/ashlar-checks.yaml @@ -0,0 +1,50 @@ +# Ashlar's CI on eom.dev's Gitea runner. +# +# Gitea runs workflows from .gitea/workflows when that directory exists in the +# pushed commit, and only falls back to .github/workflows when it doesn't. This +# file therefore stops upstream OpenMW's .github workflows (macOS, Windows and a +# full Ubuntu build) from running here, while leaving them untouched so upstream +# merges stay clean. +# +# Caveat: a ref whose commit has no .gitea/workflows, such as a freshly pushed +# upstream tag, still falls back to .github/workflows. See ASHLAR.md. +# +# The shared runner can't yet build the whole engine, so this workflow only +# runs cheap checks on Ashlar's own build tooling. A full build and test job is +# tracked in Gaming/ashlar#4 and DevOps/software-infrastructure#58 (G10). +name: Ashlar checks + +on: + push: + branches: [main] + paths: + - ".gitea/workflows/**" + - "docker/**" + workflow_dispatch: + +concurrency: + group: ${{ github.workflow }}-${{ github.ref }} + cancel-in-progress: true + +jobs: + tooling: + runs-on: ubuntu-latest + timeout-minutes: 10 + steps: + - name: Check out + uses: actions/checkout@v4 + with: + fetch-depth: 1 + + - name: Check build script syntax + run: | + status=0 + for script in docker/*.sh; do + if bash -n "$script"; then + echo "ok $script" + else + echo "FAIL $script" + status=1 + fi + done + exit "$status" diff --git a/ASHLAR.md b/ASHLAR.md index 0dcc1f932e..34a81395d6 100644 --- a/ASHLAR.md +++ b/ASHLAR.md @@ -57,6 +57,14 @@ This uses a virtual display and software rendering, then saves a screenshot to - `tes3mp-corescripts` is `https://github.com/TES3MP/CoreScripts.git`. Ashlar's `main` is based on OpenMW's `master`. Upstream's tags are kept for -reference. The `vendor/tes3mp-0.8.1` and `vendor/tes3mp-corescripts-0.8.1` +reference. + +## CI + +Ashlar's CI is `.gitea/workflows/`. Gitea ignores upstream's `.github/workflows` +only for commits that contain `.gitea/workflows`, so pushing a ref that doesn't, +such as a new upstream tag, would queue upstream's macOS and Windows jobs on the +shared runner. Don't push upstream tags or branches to `origin` until that's +handled. The `vendor/tes3mp-0.8.1` and `vendor/tes3mp-corescripts-0.8.1` branches hold TES3MP's unmodified source for reference. Multiplayer is currently out of scope.