Create a new codecov module for scorecard
Los mantenedores suelen responder en 1 día
@christoph-jerolimov ya está trabajando en esto.
Desde el 19/6/2026.
- #3477 de @fullsend-ai-coder — cerrado sin fusionar
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Scorecard is a backstage plugin and supports multiple metric, grouped as modules in folder workspaces/scorecard/plugins.
There are already modules that support GitHub, OpenSSF, SonarQube. Add a new module for codecov that provide the following metrics:
- Code coverage (Current percentage value for the default branch)
- Code coverage - Trend for the last 7 days
- Code coverage - Tracked files
- Code coverage - Tracked lines of code
- Code coverage - Covered lines of code
- Code coverage - Partial covered lines of code
- Code coverage - Missed lines of code
The metrics providers should introduce multiple new Backstage entity annotations:
codecov.io/account(string, optional)codecov.io/service(string, optional)codecov.io/owner(string, optional)codecov.io/repo(string, required to enable the codecov metrics)
All metrics providers should filter for entities with annotation codecov.io/repo.
To get the coverage from codecov.io, the backend module needs to know for which entities and codecov services it needs to communicate.
For this the backend should support multiple codecov accounts like this:
codecov:
defaultAccount: default
accounts:
- name: default
authToken: example
The authToken needs to picked up from this accounts array by the name. The account name can be specified in the annotation codecov.io/account. The default account name can be changed in the configuration. This configuration parameter should be optional. If its not specified then the default account name should use "default".
The only necessary API to get all information for all metrics is documented on https://docs.codecov.com/reference/repos_retrieve
https://api.codecov.io/api/v2/{service}/{owner_username}/repos/{repo_name}/
The authToken needs to be provided as header, but its optional and should not use it when no token is specified.
Authorization: bearer {{ ACCESS TOKEN }}
The call includes a service name, an owner username and a repo name.
serviceshould prefer the annotationcodecov.io/service, when its not defined it should automatically usegithubifgithub.com/slugannotation is defined. It should fail otherwise. Other cases might be added in the future.- owner username should prefer the annotation
codecov.io/owner. When its not defined it should try to extract an owner fromcodecov.io/repowhen it's include a slash (/). It should fail if owner is defined and repo doesn't include a slash. - repo name should prefer the annotation
codecov.io/repo. When its not defined it should try to extract an owner fromcodecov.io/repowhen it's include a slash (/).
Here is a working example API call:
curl --header 'accept: application/json' 'https://api.codecov.io/api/v2/github/redhat-developer/repos/rhdh-plugins'
This generated an out like this:
{
"name": "rhdh-plugins",
"private": false,
"updatestamp": "2026-06-19T10:29:51.283089Z",
"author": {
"service": "github",
"username": "redhat-developer",
"name": "redhat-developer"
},
"language": "typescript",
"branch": "main",
"active": true,
"activated": true,
"totals": {
"files": 2252,
"lines": 85789,
"hits": 45982,
"misses": 38246,
"partials": 1561,
"coverage": 53.59,
"branches": 24121,
"methods": 13480,
"sessions": 23,
"complexity": 0.0,
"complexity_total": 0.0,
"complexity_ratio": 0,
"diff": 0
}
}
When possible the API call response should be reused between all seven metric providers.
It is not neccessary to use a codecov dependency for this, a simple fetch call should work.
Add a type definition for the codecov response
Add tests and integrate the new module into the existing Backstage app. Add an example entity for rhdh-plugins with the annotation codecov.io/repo: redhat-developer/rhdh-plugins.
- Lenguaje dominante
- TypeScript
- Estrellas
- 50
- Forks
- 121
- Merge medio
- 1 d 14 h
- PR fusionados (30 d)
- 286
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de redhat-developer/rhdh-plugins
-
feature fullsend ready-for-triage Review effort 1/5 triaged
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
redhat-developer/rhdh-plugins#4799 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
Add entity provider implementation conventions to ai-integrations AGENTS.mdQuizá libre de nuevo Un pull request para esta issue se cerró sin fusionarse. Abiertodocumentation ready-for-triage ready-to-code Review effort 1/5 workspace/ai-integrations
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
redhat-developer/rhdh-plugins#4781 · 3 comentarios ·
Los mantenedores suelen responder en 1 día
-
Add public export surface review guidance to scorecard AGENTS.mdPosiblemente ocupada @fullsend-ai-coder la tomó hace 42 días. Abiertodocumentation ready-for-triage ready-to-code Review effort 1/5 workspace/scorecard
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
redhat-developer/rhdh-plugins#4777 · 3 comentarios ·
Los mantenedores suelen responder en 1 día
-
Add collector parameter contract assertion convention to scorecard AGENTS.mdPosiblemente ocupada @fullsend-ai-coder la tomó hace 43 días. Abiertodocumentation ready-for-triage ready-to-code workspace/scorecard
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
redhat-developer/rhdh-plugins#4734 · 3 comentarios ·
Los mantenedores suelen responder en 1 día
-
Add DORA collector pipeline and time-window boundary guidance to scorecard AGENTS.mdPosiblemente ocupada @fullsend-ai-coder la tomó hace 43 días. Abiertodocumentation ready-for-triage ready-to-code workspace/scorecard
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
redhat-developer/rhdh-plugins#4733 · 3 comentarios ·
Los mantenedores suelen responder en 1 día
Todos los issues de redhat-developer/rhdh-plugins
Issues similares
-
area: server priority: P3 type: bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
appandflow/stim#4538 ·
Los mantenedores suelen responder en 1 día
-
[BUG] Published Docker images lack the redis extra: HEADROOM_COMPRESS_SESSION_STORE stops startupPosiblemente ocupada @AlessandroSpallina la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
headroomlabs-ai/headroom#4513 ·
Los mantenedores suelen responder en 1 día
-
bug extension extension: obsidian platform: Windows
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
raycast/extensions#32838 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
copy design-review mac P3
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
tosunlab/hisarapp-core#510 ·
-
bug priority-medium to-agent
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día