Issues and Pull Requests count is wrong

Description

Contributor guide

Tech stack

javascriptreact native

Domain

mobile

Issue type

bug

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

stale

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

clear

Prerequisites

GitHub API basicsReact Native

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

40

Research direction

Investigate the GitHub API endpoint used to fetch issue/PR counts. The current implementation likely uses a search endpoint with pagination limits. Consider using the repository's open issues count and closed issues count fields from the repository API, as they reflect accurate totals. Review the code in the GitHub client service (likely in src/services or similar) to identify where the count is fetched and displayed. Check comments for alternate approaches suggested by maintainers.