Commit 3d00a85
fix(ci): skip commit-subject validation in the post-merge pipeline (#41)
## Summary
Closes #40.
`main.yaml`'s `validate` job calls `ci.yaml` as a reusable workflow,
running both `Test` and `Validate Commit Subjects` post-merge. The
commit-subject check only makes sense pre-merge (should this PR be
mergeable) - by the time `main.yaml` runs, the commits are already
merged, so re-checking their subjects is meaningless. `Test` still
re-runs post-merge (verifies the actual merge result); commit-subject
validation no longer does.
Added a `skip_commit_validation` `workflow_call` input on `ci.yaml`
(default `false`, so its own `pull_request`/`workflow_dispatch` triggers
are unaffected), and `main.yaml`'s `validate` job now passes
`skip_commit_validation: true`.
## Test plan
- [x] Both edited workflow files validated with `ruby -ryaml`
- [x] Confirmed the `if: inputs.skip_commit_validation != true`
expression safely defaults to running the job for every trigger type
that doesn't explicitly pass the input (pull_request, workflow_dispatch)
- `inputs.skip_commit_validation` evaluates to `null` there, and `null
!= true` is `true`
Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>1 parent 30dc6dc commit 3d00a85
2 files changed
Lines changed: 11 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
4 | 4 | | |
5 | 5 | | |
6 | 6 | | |
| 7 | + | |
| 8 | + | |
| 9 | + | |
| 10 | + | |
| 11 | + | |
| 12 | + | |
| 13 | + | |
| 14 | + | |
7 | 15 | | |
8 | 16 | | |
9 | 17 | | |
| |||
43 | 51 | | |
44 | 52 | | |
45 | 53 | | |
| 54 | + | |
46 | 55 | | |
47 | 56 | | |
48 | 57 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
18 | 18 | | |
19 | 19 | | |
20 | 20 | | |
| 21 | + | |
| 22 | + | |
21 | 23 | | |
22 | 24 | | |
23 | 25 | | |
| |||
0 commit comments