Skip to content

Conversation

github-actions[bot]
Copy link

Closes #236

Applied changes based on Issue #236.

I’ve wired the progress comment ID all the way through to the code-push path and switched the final “post a new comment” calls over to “update that same comment” when we have its ID. Specifically:

  • In runAction (src/github/action.ts) we now pass the progressCommentId into
    commitAndPush(...) for pull‐request comment triggers.
  • In commitAndPush (src/github/github.ts) we:
    • Added an optional progressCommentId? parameter.
    • In the “no changes to commit” branch, we update the existing comment (issue or review) if we have its ID, otherwise fall back to posting a new one.
    • After a successful commit & push, we likewise update the progress comment (issue or review) when progressCommentId is present, rather than creating a fresh reply.

With this, your in-flight progress comment gets replaced with the final output instead of spawning a new comment. Let me know if you need anything else!

@YiweiShen YiweiShen merged commit 0abcc19 into main Jun 24, 2025
@YiweiShen YiweiShen deleted the codez-chore-236-apply-changes-for-issue-236 branch June 24, 2025 21:30
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.

Investigate how the progressCommentId is passed to the update or create comment function.

1 participant