feat: distinguish new vs. previously reported conflicts in step summary
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
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
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
DeduplicationResultbut 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
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github-community-projects/pr-conflict-detector
-
enhancement keep
Difficulty 5/5 Over a week Newbie friendliness 35/100
github-community-projects/pr-conflict-detector#10 · 1 comment ·
-
enhancement keep
Difficulty 5/5 Over a week Newbie friendliness 38/100
github-community-projects/pr-conflict-detector#5 · 1 comment ·
All issues in github-community-projects/pr-conflict-detector
Similar issues
-
A new VOLTTRON_HOME starts with agent isolation mode on (string comparison of a boolean default)Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
llm translation
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
FAIRmat-NFDI/sand#239 ·
Maintainers usually reply within 1 day
-
bug P2
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
coco-research/coco#539 ·
Maintainers usually reply within 1 day
-
dependencies
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
JustBeanie/hass-volcano-hybrid#34 ·
Maintainers usually reply within 1 day