🐛 ADR Enforcer creates new comment on every review instead of updating in-place
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 6h 51m
- Merged PRs (30d)
- 104
Description
Summary
The Claude ADR Enforcer GitHub workflow creates a new comment for every PR synchronize event instead of updating the existing comment in-place. This leads to comment spam on PRs with multiple commits.
Current Behavior
Each time a PR is updated (synchronize event), the workflow posts a new comment with ADR review results.
Expected Behavior
- Summary comments: Should find and update an existing bot comment (identified by a marker like
<!-- adr-enforcer -->) rather than creating a new one - Inline review comments: Need to investigate whether these can be updated or if a new review submission is required by the GitHub API
Investigation Needed
- Check GitHub API for updating PR review comments vs creating new reviews
- Determine if inline comments can be updated or must be resubmitted
- Look at how other bots (codecov, dependabot) handle this pattern
Acceptance Criteria
- Summary comment is updated in-place on subsequent runs
- No duplicate comments from the enforcer on a single PR
- Inline review behavior is documented (update vs new review)
Contributor 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.
Research direction
Start at the Claude ADR Enforcer workflow's pull-request synchronize trigger and trace how summary and inline review comments are submitted. Check the GitHub API behavior for updating review comments, then compare how Codecov and Dependabot handle comment updates. Done means summary comments are updated without duplicates and inline review behavior is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, github-actions
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100