[DynInst_API:] [dyninst/dyninst] 5bad33: GitHub CI: don't autocancel container workflows


Date: Fri, 06 Feb 2026 15:51:47 -0800
From: Tim Haines <noreply@xxxxxxxxxx>
Subject: [DynInst_API:] [dyninst/dyninst] 5bad33: GitHub CI: don't autocancel container workflows
  Branch: refs/heads/thaines/github_nocancel_container_workflows
  Home:   https://github.com/dyninst/dyninst
  Commit: 5bad335e81cd11f3cf0132beda4913f0bea1c44f
      https://github.com/dyninst/dyninst/commit/5bad335e81cd11f3cf0132beda4913f0bea1c44f
  Author: Tim Haines <thaines.astro@xxxxxxxxx>
  Date:   2026-02-06 (Fri, 06 Feb 2026)

  Changed paths:
    M .github/workflows/dev-containers.yaml
    M .github/workflows/purge-workflows.yaml
    M .github/workflows/refresh-containers.yaml
    M .github/workflows/release-containers.yaml

  Log Message:
  -----------
  GitHub CI: don't autocancel container workflows

'Refresh base and dev containers' depends on
'Build and Deploy Development Containers'. 'Purge old workflow runs'
isn't in that dependency chain, but it could be added to a longer
workflow in the future. It doesn't matter if it is run multiple times.



To unsubscribe from these emails, change your notification settings at https://github.com/dyninst/dyninst/settings/notifications
[← Prev in Thread] Current Thread [Next in Thread→]
  • [DynInst_API:] [dyninst/dyninst] 5bad33: GitHub CI: don't autocancel container workflows, Tim Haines <=