Skip to content

Commit fc7263e

Browse files
Julianclaude
andcommitted
Add the scheduled Report caller
Runs Bowtie's reusable harness-report.yml on a schedule to publish this harness's compliance report. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1 parent e2785f4 commit fc7263e

1 file changed

Lines changed: 27 additions & 0 deletions

File tree

.github/workflows/report.yml

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
# Report this harness's Bowtie compliance on a schedule.
2+
#
3+
# The actual logic -- run the official suite against this harness's published
4+
# image and publish the per-dialect reports -- is centralized in Bowtie's
5+
# reusable `harness-report.yml`, so a change reaches every harness at once.
6+
# Bowtie's central report workflow then collects and combines each harness's
7+
# published report.
8+
name: Report
9+
10+
on:
11+
workflow_dispatch:
12+
schedule:
13+
# Every 6 hours. `bowtie site collect` pins the suite to a per-hour commit,
14+
# so every harness running in the same hour reports against the same suite.
15+
# The minute is staggered per repository during rollout to spread load.
16+
- cron: "20 */6 * * *"
17+
18+
permissions: {}
19+
20+
jobs:
21+
report:
22+
# The template itself has no real harness image to report on.
23+
if: github.repository != 'bowtie-json-schema/test-harness-template'
24+
permissions:
25+
contents: write # to publish the report release
26+
packages: read # to pull the harness's own image
27+
uses: bowtie-json-schema/bowtie/.github/workflows/harness-report.yml@0e63bcfce60f317c928b1ac141dcaebdcc14ce29 # main

0 commit comments

Comments
 (0)