You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The safety check was blocking docs-only commits whenever the previous
master commit had ANY running workflows, even if they hadn't failed yet.
This created a bottleneck when workflows were slow (e.g., integration tests).
Changes:
- Allow docs-only skips when previous workflows are running (not failed yet)
- Only block if completed workflows have actually failed
- Add informative logging about running vs failed workflows
Rationale:
- Running workflows haven't failed yet → no known issue to block on
- They will complete and validate the previous commit independently
- Eliminates bottleneck from slow-running workflows
- Still maintains safety by blocking on actual failures
Fixes the circular dependency issue where docs-only commits couldn't
merge because previous commit's workflows were still in progress.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <[email protected]>
// No jobs found - skip this run (don't treat as failing)
133
+
core.warning(`No jobs found for workflow run ${run.id} (${run.name}). Skipping.`);
126
134
continue;
127
135
}
128
136
@@ -150,7 +158,11 @@ runs:
150
158
}
151
159
152
160
if (failingRuns.length === 0) {
153
-
core.info(`Previous master commit ${previousSha} completed without failures. Docs-only skip allowed.`);
161
+
if (incompleteRuns.length > 0) {
162
+
core.info(`Previous master commit ${previousSha} has ${incompleteRuns.length} running workflow(s) but no completed failures. Docs-only skip allowed.`);
163
+
} else {
164
+
core.info(`Previous master commit ${previousSha} completed without failures. Docs-only skip allowed.`);
0 commit comments