checkstyle / checkstyle/patch-filters
Report on files being validated against
- Dominant language
- Java
- Stars
- 4
- Forks
- 11
- Avg merge
- 5h 55m
- Merged PRs (30d)
- 2
Description
Identified at https://github.com/checkstyle/eclipse-cs/pull/380#issuecomment-1310507743 ,
It was not clear why we were getting random issues and then it became clear patch-filters prevented a Checkstyle run in some cases, which is its purpose.
It would be helpful if patch-filters reported something minor like "No files identified as changed" or "Identified X files as changed" so it is clear when allows Checkstyle to run and not run.
I don't think it would have helped this case, but it will make what it is doing clearer.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the patch-filters logic that identifies changed files and decides whether to run Checkstyle; no source file or test is named in the issue. Trace that decision path and its existing output. Done means the filter reports when no files were found or how many files were identified, making the Checkstyle decision understandable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing-qa, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100