Skip to content
pr

Chore: [AEA-0000] - use published dev container #239

Sign in to view logs

Chore: [AEA-0000] - use published dev container

Chore: [AEA-0000] - use published dev container #239

Triggered via pull request February 16, 2026 18:52
@anthony-nhsanthony-nhs
synchronize #65
use_published_dev_container
Status Success
Total duration 2m 55s
Artifacts 3

pull_request.yml

on: pull_request
get_config_values
3s
get_config_values
pr_title_format_check  /  pr_title_format_check
4s
pr_title_format_check / pr_title_format_check
quality_checks  /  quality_checks
2m 3s
quality_checks / quality_checks
quality_checks  /  IaC-validation
43s
quality_checks / IaC-validation
quality_checks  /  get_docker_images_to_scan
6s
quality_checks / get_docker_images_to_scan
Matrix: quality_checks / docker_vulnerability_scan
tag_release  /  install_semantic_release
20s
tag_release / install_semantic_release
dependabot-auto-approve-and-merge  /  dependabot
0s
dependabot-auto-approve-and-merge / dependabot
tag_release  /  tag_release
18s
tag_release / tag_release
Fit to window
Zoom out
Zoom in

Artifacts

Produced during runtime
Name Size Digest
asdf_artifact
232 MB
sha256:235fc50fd8a509e699c23b266fa70ed116d1b1aa9a2bed738439a7c32a8464b0
config_artifact
1.11 KB
sha256:d10ad67d9d3244554e64a29dd4fcab7c913f49e90572a93d2a2537a5cce78796
sbom.cdx.json
22.9 KB
sha256:648a3e0b0e039553e98d8c88a580e64b1e76ed1688f1307bad91db49e9be3176