PR #86 introduced several configuration changes to the JaCoCo CI workflow (.github/workflows/jacoco_report.yml) that deserve follow-up documentation and standardization work:
Coverage threshold inconsistency — coverage-per-changed-file was raised from 0.0 to 60.0, while coverage-overall and coverage-changed-files remain at 80.0. There's no documented rationale for these different thresholds. A decision should be made and documented on the intended coverage standards across the project.
Python dependency not obvious — A Python 3.14 setup step was added as a hidden dependency of the updated MoranaApps/jacoco-report action. This is not obvious to contributors and should be documented (e.g., in CONTRIBUTING.md or via inline comments).
Pinned action SHA — no update strategy — The jacoco-report action is pinned to a specific commit SHA (f9dc5ba..., v3.0.1). There is no documented process for keeping this pinned action up-to-date. Consider using Dependabot or documenting a manual update checklist.
PR #86 introduced several configuration changes to the JaCoCo CI workflow (.github/workflows/jacoco_report.yml) that deserve follow-up documentation and standardization work:
Coverage threshold inconsistency — coverage-per-changed-file was raised from 0.0 to 60.0, while coverage-overall and coverage-changed-files remain at 80.0. There's no documented rationale for these different thresholds. A decision should be made and documented on the intended coverage standards across the project.
Python dependency not obvious — A Python 3.14 setup step was added as a hidden dependency of the updated MoranaApps/jacoco-report action. This is not obvious to contributors and should be documented (e.g., in CONTRIBUTING.md or via inline comments).
Pinned action SHA — no update strategy — The jacoco-report action is pinned to a specific commit SHA (f9dc5ba..., v3.0.1). There is no documented process for keeping this pinned action up-to-date. Consider using Dependabot or documenting a manual update checklist.