Skip to content

Comments

check for empty logs after pipeline runs#1443

Merged
freekmurze merged 1 commit intomainfrom
fix/empty-logs-after-pipe
Jan 31, 2026
Merged

check for empty logs after pipeline runs#1443
freekmurze merged 1 commit intomainfrom
fix/empty-logs-after-pipe

Conversation

@freekmurze
Copy link
Member

Summary

  • Fixed issue where empty log entries were created even when a pipe removed all changes
  • The check for empty logs (dontSubmitEmptyLogs) was happening before the pipeline ran
  • Moved the empty log check to after the pipeline has processed the changes
  • Added test to verify that logs are not created when a pipe removes all changes and dontSubmitEmptyLogs is set

Fixes #1430

🤖 Generated with Claude Code

The check for empty logs was happening before the pipeline ran, so if a
pipe removed all changes, an empty log entry would still be created.

Moved the empty log check to after the pipeline has processed the changes.

Fixes #1430

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@freekmurze freekmurze merged commit 980240f into main Jan 31, 2026
31 checks passed
@freekmurze freekmurze deleted the fix/empty-logs-after-pipe branch January 31, 2026 12:21
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.

stop logging empty changes after pipe manipulation

1 participant