Adding code coverage to CI
@paloma-martinez is already working on this.
Since Nov 24, 2025.
Assessment
This issue has not been assessed yet.
Description
To ensure the reliability of our code, this issue is dedicated to the implementation of a Github action to add code coverage evaluation to the CI.
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
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.
More from GEOS-DEV/geosPythonPackages
-
type: refactor
GEOS-DEV/geosPythonPackages#249 · 1 assignee ·
-
type: feature
Difficulty 3/5 1-2 days Newbie friendliness 35/100
GEOS-DEV/geosPythonPackages#243 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
GEOS-DEV/geosPythonPackages#226 ·
-
GEOS-DEV/geosPythonPackages#213 · 1 comment · 1 reaction · 1 assignee ·
-
trame-UI
GEOS-DEV/geosPythonPackages#202 · 1 assignee ·
All issues in GEOS-DEV/geosPythonPackages
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
zostera/django-bootstrap4#894 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
use-agent-os/agent-os#3276 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
zephyrproject-rtos/zephyr#119726 ·
-
area/auth bug comp/agent P3 platform/discord type/security
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NousResearch/hermes-agent#117848 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
zilliztech/memsearch#759 ·