fix: handle deleted tracking comment gracefully in update-comment-link #23
Conversation
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
varin-nair-factory
added a commit
that referenced
this pull request
Jan 29, 2026
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
The update-comment-link.ts step fails with exit code 1 when the tracking comment (created at the start of a Droid run) no longer exists by the time the job finishes. This can happen when:
• A user manually deletes the comment
• GitHub's spam filter removes it
• Another automation cleans it up
This causes the entire workflow to be marked as failed even though the actual review/action completed successfully.
Solution
Add graceful handling for 404 errors when fetching the tracking comment. When the comment is not found:
• Log an informational message explaining the situation
• Exit with code 0 (success) instead of failing
This ensures the workflow status reflects the actual outcome of the Droid execution rather than failing on a non-critical post-processing step.