feat: distinguish new vs. previously reported conflicts in step summary

Open
#45 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github-actions, python
Domain
ci-cd

Research direction

Start by tracing the deduplication module's DeduplicationResult into the markdown writer used for the step summary and output report. Confirm how new, changed, unchanged, and resolved conflicts are represented, then update the report so each category is distinguished as described, with unchanged conflicts collapsed or separated. Verify the generated summary includes the requested counts and conflict listings.

Written by the indexing model from the issue text.

Description

keep

Problem

The GitHub Actions step summary reports the total conflict count (e.g., "Found 37 potential conflicts across 2 repositories") but does not indicate which conflicts are new since the last run. Users scanning the summary have no way to tell what changed without comparing to the previous run manually.

For example, a recent run on github/new-user-experience showed:

Total: 37 potential conflict(s) across 2 repo(s)
Deduplication: 6 new, 0 changed, 31 unchanged, 1 resolved

The deduplication data is in the logs but not surfaced in the step summary. Only 6 of the 37 conflicts were new, yet the summary treats them all equally.

Proposed Solution

Add a section to the step summary that highlights what changed since the last run:

  • New conflicts (6) - listed prominently at the top
  • Changed conflicts (0) - conflicts where the overlapping files/lines changed
  • Unchanged conflicts (31) - collapsed or in a separate section
  • Resolved conflicts (1) - conflicts that are no longer detected

This would let users quickly see "6 new conflicts to review" instead of having to mentally diff 37 total conflicts against the last run.

Example summary structure
## PR Conflict Report

### 🆕 6 New Conflict(s)
[table of new conflicts]

### 🔄 0 Changed Conflict(s)

### ✅ 1 Resolved Conflict(s)
[table of resolved conflicts]

<details>
<summary>31 Unchanged Conflict(s)</summary>
[table of unchanged conflicts]
</details>

Additional Context

  • The deduplication module already categorizes conflicts as new/changed/unchanged/resolved
  • This data is passed through as DeduplicationResult but the markdown writer does not use it
  • The step summary and output report currently just list all conflicts without differentiation
Dominant language
Python
Stars
4
Forks
1
Avg merge
5h 55m
Merged PRs (30d)
9

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github-community-projects/pr-conflict-detector

All issues in github-community-projects/pr-conflict-detector

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.