Fix contributor fallback limit when automated accounts are present
Maintainers usually reply within 1 day
Assessment
This issue has not been assessed yet.
Description
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.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 5
Getting set up
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 Imageomics/OpenCite
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Imageomics/OpenCite#66 ·
Maintainers usually reply within 1 day
-
YAML Field Apostrophe Quotes Parsing IssuePossibly taken @NetZissou claimed this 1 day ago. Openbug
Imageomics/OpenCite#76 · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Imageomics/OpenCite#73 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 65/100
Imageomics/OpenCite#68 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
Imageomics/OpenCite#69 ·
Maintainers usually reply within 1 day
All issues in Imageomics/OpenCite
Similar issues
-
refactor
Difficulty 2/5 Half a day Newbie friendliness 84/100
Maintainers usually reply within 5 days
-
translation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ciderapp/translations#87 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
component: split-view platform: windows
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
zen-browser/desktop#15616 · 1 reaction ·
Maintainers usually reply within 1 day