getappmap / getappmap/appmap-js
CI Findings report separates "legacy" findings from new ones
Open
Nobody has claimed this yet.
appmap-analysis
enhancement
- Dominant language
- TypeScript
- Stars
- 53
- Forks
- 18
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 8
Description
When analysis is applied to a PR for the first time, all the legacy / latent findings in the codebase are reported. This is overwhelming to the user.
Report legacy findings in a separate, collapsed section.
Contributor guide
No contributing guide indexed for this repository
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 by locating the CI Findings report and the code that distinguishes legacy or latent findings from new findings. Reproduce analysis on a PR for the first time, then verify that legacy findings appear in a separate collapsed section rather than overwhelming the main report.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100