Skip to content

Skip follower databases with no changes in diff output#166

Merged
alex-slynko merged 2 commits intomainfrom
skip-empty-follower-diffs
Apr 14, 2026
Merged

Skip follower databases with no changes in diff output#166
alex-slynko merged 2 commits intomainfrom
skip-empty-follower-diffs

Conversation

@alex-slynko
Copy link
Copy Markdown
Contributor

When follower databases have no changes, the diff output previously printed empty headers like:

# Changes for follower database ghti-follower.eastus/hydro
# Changes for follower database copilotlimiter.eastus/hydro

This filters out follower diffs with empty change lists so they are omitted entirely from both the markdown and structured diff output.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings April 14, 2026 07:01
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR improves diff output readability by omitting follower database sections entirely when there are no follower changes, preventing empty headers from appearing in both markdown and structured diff results.

Changes:

  • Filter FollowerDiffs to only those with Changes.Count > 0 when generating structured diff output.
  • Apply the same filtering when generating markdown diff output (and associated logging).
Show a summary per file
File Description
KustoSchemaTools/KustoSchemaHandler.cs Skips follower diffs with empty change lists in both structured and markdown diff generation.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

  • Files reviewed: 1/1 changed files
  • Comments generated: 0

@alex-slynko alex-slynko merged commit adce341 into main Apr 14, 2026
5 checks passed
@alex-slynko alex-slynko deleted the skip-empty-follower-diffs branch April 14, 2026 09:22
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