---
title: "Discussion on \"The agent reported CI green, but the check had never run on the commit it pushed\" | Hashnode"
description: "Discussion on \"The agent reported CI green, but the check had never run on the commit it pushed\". The agent amended the fix, force-pushed, polled the check it already knew about, saw green, and reported the PR ready. That verdict belonged to the previous SHA. The new commit had no run at all. Green means nothing until the check is tied to the exact HEAD."
url: "https://hashnode.com/posts/agent-ci-green-on-stale-commit/6ada81acb87a9ae7d554dba8"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [The agent reported CI green, but the check had never run on the commit it pushed](https://blogs.powerduck.com/agent-ci-green-on-stale-commit?utm_source=hashnode&utm_medium=feed)

The agent amended the fix, force-pushed, polled the check it already knew about, saw green, and reported the PR ready. That verdict belonged to the previous SHA. The new commit had no run at all. Green means nothing until the check is tied to the exact HEAD.

Oct 22 · 4 min read · blogs.powerduck.com  
Read the article

-   [#aiagents](https://hashnode.com/tag/aiagents)
-   [#cicd](https://hashnode.com/tag/cicd)
-   [#pr](https://hashnode.com/tag/pr)
-   [#workflow](https://hashnode.com/tag/workflow)

## Written by

[Powerduck](https://hashnode.com/@powerduck)

@powerduck · hon

  
[View profile](https://hashnode.com/@powerduck)

## Responses 1

Markdown supported · ⌘↵ to post

[netproxy](https://hashnode.com/@argumentmoney8117)

[Oct 22](https://hashnode.com/posts/agent-ci-green-on-stale-commit/6ada81acb87a9ae7d554dba8/comment/6ada8dfeb394e0e95320e018)

Good articulation of a failure mode I have run into as well: polling by check name instead of by commit SHA. The checklist at the end is the part I will reuse — requiring the summary to name the commit, not just the verdict, is a simple rule that transfers to any agent workflow.
