Skip to content

feat(report-back): fleet members report back to the Hypatia verdict grid #1987

feat(report-back): fleet members report back to the Hypatia verdict grid

feat(report-back): fleet members report back to the Hypatia verdict grid #1987

Workflow file for this run

# This workflow is managed by gh actions-lock.
# SPDX-License-Identifier: MPL-2.0
# This workflow is managed by gh actions-lock.
# This workflow is managed by gh actions-lock.
# Thin wrapper around hyperpolymath/standards hypatia-scan-reusable.yml.
# See standards#191 for the reusable's purpose and design.
name: Hypatia Security Scan
on:
push:
branches: [main, master, develop]
# No `branches:` filter — a required check whose workflow is branch-gated is
# never created on a non-matching base and blocks merge forever at
# "Expected — Waiting for status to be reported" (cf. affinescript#645).
pull_request:
schedule:
- cron: '0 0 * * 0'
workflow_dispatch:
# Estate guardrail: cancel superseded runs so re-pushes don't pile up.
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
permissions:
actions: read
contents: read
security-events: write
pull-requests: write
jobs:
hypatia:
uses: hyperpolymath/standards/.github/workflows/hypatia-scan-reusable.yml@75bd5994470661a099df562d6d5ad2fe744dbd66

Check failure on line 34 in .github/workflows/hypatia-scan.yml

View workflow run for this annotation

GitHub Actions / .github/workflows/hypatia-scan.yml

Invalid workflow file

error parsing called workflow ".github/workflows/hypatia-scan.yml" -> "hyperpolymath/standards/.github/workflows/hypatia-scan-reusable.yml@75bd5994470661a099df562d6d5ad2fe744dbd66" : workflow was not found. See https://docs.github.com/actions/learn-github-actions/reusing-workflows#access-to-reusable-workflows for more information.
# hypatia-scan-reusable declares one secret; pass that one, not everything.
secrets:
HYPATIA_SCAN_PAT: ${{ secrets.HYPATIA_SCAN_PAT }}
# Total caller-side wall-clock cap for the reusable. Matches
# Hypatia's `missing_timeout_minutes` rule expectation. The scan is
# typically ~3 min; the cap leaves headroom for slow estate builds.