fix: remove ci_run_id from Rule 1 condition to support Cloud Build repos#48
Merged
Conversation
ci_run_id is unavailable for non-GitHub-Actions CI (e.g. Cloud Build). The previous Rule 1 triggered on empty ci_run_id regardless of CI outcome, causing all Cloud Build PRs to be labeled ai-skipped-ci-failed even when CI passed. Rule 1 now only checks ci_conclusion; ci_run_id emptiness only affects whether Step 2 log analysis can run.
coolbitxColma
approved these changes
Jun 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Rule 1 in Claude's prompt had the condition:
For repos using Cloud Build (not GitHub Actions),
ci_run_idis always empty. This meant Rule 1 always triggered regardless of whether CI actually passed, labeling every Dependabot PR asai-skipped-ci-failed.Fix
ci_conclusion is not "success"— emptyci_run_idno longer affects the decisionci_run_idis non-empty; ifci_run_idis empty and CI failed, the comment shows "N/A — CI run ID unavailable, check CI provider directly"ci_conclusion is "success"(removed theci_run_id is non-emptyrequirement, since codebase grep doesn't need a run ID)Impact
ci_run_idis always providedai-skipped-ci-failedwith N/A in failure details