Skip to content

Conversation

@motatoes
Copy link
Contributor

@motatoes motatoes commented Jan 22, 2026

This change implements automatic success for the digger/apply check when all plan jobs complete with zero infrastructure changes, eliminating the need for manual intervention in no-change scenarios.

Changes:

  • Create both digger/plan and digger/apply checks when PR opens with plan jobs
  • The apply check starts in "queued" state with message indicating it will auto-succeed if no changes are detected
  • After plan batch completes successfully, detect if all jobs have zero changes (ResourcesCreated = 0, ResourcesUpdated = 0, ResourcesDeleted = 0)
  • If all jobs have zero changes, automatically update apply check to "completed" with "success" conclusion
  • Add GetCheckRunsForCommit() method to query check runs for a commit SHA

Benefits:

  • Improved UX: Users see both checks immediately when PR opens
  • Automation: No manual action needed for zero-change plans
  • Clear communication: Check messages explain the automatic behavior
  • No breaking changes: Existing behavior for plans with changes unchanged

🧠 Ai UsageDetails (if applicable):

Used cursor to ship this feature in a directed way, reviewed the code and tested it myself

IMPORTANT: Please disclose any usage of ai tooling while making this change. If you did not use any AI write "NA" below

Example: Used ChatGPT to help with doc phrasing.
Example: Code generated by Copilot; reviewed and verified manually.

This change implements automatic success for the digger/apply check when
all plan jobs complete with zero infrastructure changes, eliminating the
need for manual intervention in no-change scenarios.

Changes:
- Create both digger/plan and digger/apply checks when PR opens with plan jobs
- The apply check starts in "queued" state with message indicating it will
  auto-succeed if no changes are detected
- After plan batch completes successfully, detect if all jobs have zero changes
  (ResourcesCreated = 0, ResourcesUpdated = 0, ResourcesDeleted = 0)
- If all jobs have zero changes, automatically update apply check to "completed"
  with "success" conclusion
- Add GetCheckRunsForCommit() method to query check runs for a commit SHA

Benefits:
- Improved UX: Users see both checks immediately when PR opens
- Automation: No manual action needed for zero-change plans
- Clear communication: Check messages explain the automatic behavior
- No breaking changes: Existing behavior for plans with changes unchanged

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Copy link
Contributor

@breardon2011 breardon2011 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

approve

@motatoes motatoes merged commit 88d866b into develop Jan 23, 2026
19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants