Compact the accumulated review state in the PR comment
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- github, typescript
Research direction
Start by locating the runner code that handles review_state_truncated and the persistent review comment state, then trace how active and resolved findings are stored and recognized. Compare the listed compaction options against T01 and T02, and inspect the fingerprint test referenced in T03. Done means the state stays below GitHub’s limit across many runs, earlier findings remain recognized, and the test flags changes to the compacted function.
Written by the indexing model from the issue text.
Description
Background
The runner detects when the persistent review comment reaches GitHub's size limit (error code review_state_truncated). PR-Agent 0.47.0 keeps all active findings and only limits resolved findings to 20. Once the state is full, every later review of that pull request ends as failed.
Goal
Compact the accumulated state so that long-lived pull requests with many pushes do not hit the limit, without making recognition of earlier findings worse. Options to evaluate:
- shorten the stored texts
- summarize very old active findings
- lower the limit for resolved findings
- start a new comment when the state is full
Test cases
| ID | Case | Level | Expectation |
|---|---|---|---|
| T01 | PR with 100 active findings over many runs | Engine | The comment stays below the limit, no review_state_truncated |
| T02 | A finding from an early run shows up again | Engine | It is recognized as known |
| T03 | A PR-Agent update changes the compacted function | Unit | The fingerprint test fails and flags the change |
Migrated from Jira CR-52 (original test IDs CR-52-T01 to T03).
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- Avg merge
- 1h 18m
- Merged PRs (30d)
- 186
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 ExpidetGames/code-reviewer
-
area: app type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
ExpidetGames/code-reviewer#308 ·
Maintainers usually reply within 1 day
-
type: docs
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ExpidetGames/code-reviewer#94 ·
Maintainers usually reply within 1 day
-
area: app post-mvp type: feature
Difficulty 5/5 Over a week Newbie friendliness 12/100
ExpidetGames/code-reviewer#339 ·
Maintainers usually reply within 1 day
-
area: runner post-mvp type: feature
Difficulty 5/5 Over a week Newbie friendliness 18/100
ExpidetGames/code-reviewer#338 ·
Maintainers usually reply within 1 day
-
area: runner post-mvp type: feature
Difficulty 5/5 Over a week Newbie friendliness 12/100
ExpidetGames/code-reviewer#337 ·
Maintainers usually reply within 1 day
All issues in ExpidetGames/code-reviewer
Similar issues
-
streams:add
Difficulty 2/5 Under an hour Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
apache/rocketmq-dashboard#6872 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
interledger/publisher-tools#931 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ARTPARK-SAHAI-ORG/calibrate-frontend#727 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
fab-geocommuns/RNB-site#539 ·
Maintainers usually reply within 2 days