Skip to content

add workflow_dispatch handling and crucible-ci concurrency - #161

Merged
k-rister merged 2 commits into
masterfrom
workflow-updates
Mar 17, 2026
Merged

add workflow_dispatch handling and crucible-ci concurrency#161
k-rister merged 2 commits into
masterfrom
workflow-updates

Conversation

@k-rister

Copy link
Copy Markdown
Contributor

Summary

  • Ensure workflow_dispatch triggers always run real CI (not the faux path), since there is no PR context for tj-actions/changed-files to evaluate
  • Add concurrency group to crucible-ci.yaml so concurrent runs on the same ref cancel in-progress ones (matching the pattern in cdm-ci.yaml and crucible repo workflows)

Test plan

  • Verify workflow_dispatch runs real CI for both cdm-ci and crucible-ci
  • Verify doc-only PRs still take the faux path
  • Verify non-doc PRs still take the real CI path
  • Verify concurrent crucible-ci runs on the same ref cancel properly

🤖 Generated with Claude Code

k-rister and others added 2 commits March 17, 2026 16:32
Without workflow_dispatch guards, manual triggers have no PR context so
tj-actions/changed-files reports no changes, causing neither real nor faux
CI to run. Add workflow_dispatch conditions so manual triggers always take
the real CI path.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@k-rister
k-rister merged commit d13b833 into master Mar 17, 2026
9 checks passed
@github-project-automation github-project-automation Bot moved this from In Progress to Done in Crucible Tracking Mar 17, 2026
@k-rister
k-rister deleted the workflow-updates branch March 17, 2026 22:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants