Files
awoooi/docs/operations/templates/awoooi-gitea-onboarding-warning-step.workflow.yaml
ogt d41a1d37fe
Some checks failed
CD Pipeline / workflow-shape (push) Successful in 1s
CD Pipeline / cancel-stale-cd (push) Has been skipped
CD Pipeline / build-and-deploy (push) Has been cancelled
CD Pipeline / post-deploy-checks (push) Has been cancelled
CD Pipeline / tests (push) Has been cancelled
fix(ci): keep workflows on Gitea supply chain
2026-07-11 00:35:10 +08:00

53 lines
1.8 KiB
YAML

# AWOOOI Gitea Onboarding Warning Step template.
#
# Controlled runtime:
# - no push / pull_request / pull_request_target trigger
# - no generic runner labels
# - runtime warning-step job is enabled for controlled workflow_dispatch only
# - no secrets, host writes, workflow dispatch from this commit, or product writes
name: AWOOOI Onboarding Warning Step
on:
workflow_dispatch:
env:
AWOOOI_ONBOARDING_WARNING_STEP_EXECUTION_ENABLED: "1"
jobs:
workflow-shape:
# Gitea 1.25 can mark a workflow invalid when every root job has a job-level
# `if`. Keep this no-op root job so the workflow remains parseable while
# the runtime warning-step job below stays behind the controlled switch.
runs-on: awoooi-non110-host
timeout-minutes: 1
steps:
- name: Confirm controlled warning-step workflow shape
run: echo "warning-step runtime job is enabled for controlled workflow_dispatch only."
warning-step:
if: ${{ env.AWOOOI_ONBOARDING_WARNING_STEP_EXECUTION_ENABLED == '1' }}
runs-on: awoooi-non110-host
timeout-minutes: 3
steps:
- name: Checkout source from Gitea
env:
GITEA_SOURCE_URL: http://192.168.0.110:3001/wooo/awoooi.git
run: |
set -euo pipefail
git init .
git remote remove origin 2>/dev/null || true
git remote add origin "$GITEA_SOURCE_URL"
git fetch --no-tags --prune --depth=1 origin "$GITHUB_SHA"
git checkout --force --detach FETCH_HEAD
- name: Validate warning-step boundaries
run: |
set -euo pipefail
python3 ops/runner/guard-gitea-runner-pressure.py --root .
git diff --check
cat <<'SUMMARY'
AWOOOI onboarding warning step template is present.
Runtime execution is enabled only for controlled workflow_dispatch boundary validation.
SUMMARY