Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Fix contributor fallback limit when automated accounts are present

Open
#56 1 comment 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@beanbean9339 is already working on this.

Since Sep 10, 2026.

  • #63 by @beanbean9339 — merged

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Imageomics/OpenCite

All issues in Imageomics/OpenCite

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.