Pipeline check — 2026-08-17 #8

Title

Pipeline check — 2026-08-17

Organization

BCHC Template QA

What is being shared

Playbook or write-up

Area of work

Data & informatics, Finance, procurement & contracts, IT & operations

Stage

Pilot

Summary

An end-to-end verification entry that exercises the issue → pull request → Pages pipeline. It is deleted again as soon as the check is finished.

Result in one line

Confirms the submission pipeline end to end in one pass

How AI is involved

AI was used to build it

Types of AI

• Generative text (LLM)
• Chat assistant
• Agents & automation

AI tools & models

Claude Opus 5
GitHub Actions

Where it runs

On-premises, Desktop or local

Vendor or partner

No response

Skills needed to set it up

Developer

Readiness

Reference only, Human review built in

Source code

https://github.com/crypticpy/bchc-template

Live site or demo

No response

Documentation or write-up

https://github.com/crypticpy/bchc-template/blob/main/docs/admin-guide.md

Other resources

Admin guide | https://github.com/crypticpy/bchc-template/blob/main/docs/admin-guide.md

Screenshots

https://raw.githubusercontent.com/crypticpy/bchc-template/main/catalog/epi-signal-triage/screenshots/01.png | Signal triage queue, used here as a pipeline test image

Data it touches

Public data only

Data sources

None — this is a synthetic test entry.

Who sees the output

Internal staff

Contact name

Pipeline Check

Contact email

pipeline-check@example.org

Full write-up

Problem

Wave 1 of the contributor-panel work could only be tested locally. The issue → scaffold → pull request → Pages → "it's live" path had never run on the real repository.

Approach

Open a submission through the real issue form body format, watch the workflows, and delete the entry again.

Not a real section

This heading sits inside the write-up and must not be parsed as a field answer.

Results

Recorded in the wave 2 U8 report.

Lessons learned

Recorded in the wave 2 U8 report.

How to reuse this

Do not — this entry is removed by a follow-up pull request.