Fix contributor fallback limit when automated accounts are present
Los mantenedores suelen responder en 1 día
Evaluación
Este issue todavía no se ha evaluado.
Descripción
During testing of the GitHub metadata importer with Imageomics/catalog, automated accounts appear to be counted toward the contributor fallback limit before being filtered out.
The importer reported:
"Excluded 3 automated account(s) from fallback authors."
However, the repository has additional human contributors that were not included. This suggests that the fallback limit may currently be applied to the raw GitHub contributor list before automated accounts are excluded.
Expected Behavior
The contributor fallback limit should apply to the number of eligible human contributors selected as fallback authors, rather than the number of raw GitHub contributor accounts encountered.
For example, if the fallback limit is 5 and some of the first contributors are automated accounts, the importer should continue evaluating contributors until it has found up to 5 eligible human contributors, subject to a reasonable maximum/safety limit.
Additional Observation
Testing with Imageomics/got-milk-monarchs also showed that Dylan was not picked up as a contributor. This may be expected because his GitHub profile does not appear to provide a usable display name. The desired behavior for contributors with incomplete profile information should be documented as part of this work.
Acceptance Criteria
- Automated accounts do not consume the human contributor fallback limit.
- The importer continues through contributor pagination as needed to find eligible human contributors.
- Existing automated-account detection and filtering remain intact.
- Existing contributor ordering and deduplication behavior remain unchanged.
- Expected behavior for contributors without a usable GitHub display name is documented.
- Add regression tests covering automated accounts appearing before eligible human contributors.
- Lenguaje dominante
- JavaScript
- Estrellas
- 0
- Forks
- 0
- Merge medio
- 1 d 23 h
- PR fusionados (30 d)
- 5
Preparar el entorno
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 Imageomics/OpenCite
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Imageomics/OpenCite#66 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
Imageomics/OpenCite#73 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 65/100
Imageomics/OpenCite#68 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 3/5 1-2 días Aptitud para principiantes 68/100
Imageomics/OpenCite#69 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 3/5 1-2 días Aptitud para principiantes 62/100
Imageomics/OpenCite#55 ·
Los mantenedores suelen responder en 1 día
Todos los issues de Imageomics/OpenCite
Issues similares
-
Design only Leadership Survey SLFS
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
bcgov/digital-journeys#2293 ·
-
Toolkit
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
Los mantenedores suelen responder en 1 día
-
API Bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
ProjectSidewalk/SidewalkWebpage#5556 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
jessepollak/home#1454 ·
Los mantenedores suelen responder en 1 día
-
Mend: dependency security vulnerability untriaged
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
opensearch-project/OpenSearch-Dashboards#12822 ·
Los mantenedores suelen responder en 1 día