Skip to content

ci: add workflow_dispatch dev release for sash #52 E2E testing - #103

Draft
qclayssen wants to merge 3 commits into
mainfrom
feat/sash52-dev-release
Draft

ci: add workflow_dispatch dev release for sash #52 E2E testing#103
qclayssen wants to merge 3 commits into
mainfrom
feat/sash52-dev-release

Conversation

@qclayssen

Copy link
Copy Markdown
Contributor

Summary

Adds a manually-triggered (workflow_dispatch) GitHub Actions workflow to build and push a dev Docker image, for E2E-testing sash #52 (PCGR skip on high variant count) fixes before they're formally released.

Fixed before opening this PR (caught by review): the original commit logged into docker.io using DOCKERHUB_USERNAME/DOCKERHUB_TOKEN secrets — neither is configured on this repo (verified via gh secret list), so every run would have failed at the login step. It also pushed to a personal Docker Hub account, the same anti-pattern flagged as a blocking governance finding in the sash 0.7.0 release audit (qclayssen/sigrap:0.2.0-dev-7). Switched to ghcr.io/umccr/gpgr using the built-in GITHUB_TOKEN, matching this repo's existing deploy.yaml convention exactly — no new secrets required.

Test plan

  • YAML structurally validated
  • Registry/auth pattern matches deploy.yaml (already in production use)
  • Not yet run via workflow_dispatch — first real trigger will be the actual validation

qclayssen added 3 commits May 25, 2026 09:55
Regression guard: 563f946 accidentally re-introduced required=TRUE,
causing crashes on samples without DRAGEN HRD files.
Builds and pushes linux/amd64 Docker image to docker.io on demand.
Requires DOCKERHUB_USERNAME and DOCKERHUB_TOKEN repo secrets.
…b account

Original workflow logged into docker.io using DOCKERHUB_USERNAME/
DOCKERHUB_TOKEN secrets, neither of which is configured on this repo
(confirmed via gh secret list) — every run would fail at the login
step. It also pushed to a personal Docker Hub account, the same
governance anti-pattern flagged as a blocking finding in the sash
0.7.0 release audit (qclayssen/sigrap:0.2.0-dev-7).

Switched to ghcr.io/umccr/gpgr using GITHUB_TOKEN, matching the
existing deploy.yaml convention exactly — no new secrets needed.
@qclayssen
qclayssen marked this pull request as draft July 15, 2026 06:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant