Commit 1a7ed1d
committed
ci-artifacts: also run on pushes to the
The PR opened from this branch (#117) keeps diverging from `main` (the
package-sync commits keep landing there, and the conversion commits
keep removing the MINGW64 tree here), so the merge commit GitHub
builds for the `pull_request` event is `DIRTY` most of the time. While
in that state, GitHub skips the `pull_request` workflow dispatch
entirely, which means `ci-artifacts` no longer runs against the PR
head and we lose all signal about whether the converted SDK still
builds Git.
Adding `ucrt64` to the workflow's `push` trigger sidesteps that:
pushes to the branch run the workflow directly, without going through
a synthetic merge commit, so the build/test matrix stays exercised
until the branch is finally merged.
Assisted-by: Opus 4.7
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>ucrt64 branch1 parent e1ffa1f commit 1a7ed1d
1 file changed
Lines changed: 1 addition & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
4 | 4 | | |
5 | 5 | | |
6 | 6 | | |
| 7 | + | |
7 | 8 | | |
8 | 9 | | |
9 | 10 | | |
| |||
0 commit comments