refactor: rename RepositoryNode.issues field to recent_issues

[miran786]

Description

The issues field resolver on RepositoryNode is misleadingly named — it does not return all issues for a repository. It returns only the most recent ones, limited by RECENT_ISSUES_LIMIT = 5.

File: backend/apps/github/api/internal/nodes/repository.py, line 51

@strawberry_django.field(prefetch_related=["issues"])
def issues(self, root: Repository) -> list[IssueNode]:
    """Resolve recent issues."""
    # TODO(arkid15r): rename this to recent_issues.
    return root.issues.order_by("-created_at")[:RECENT_ISSUES_LIMIT]

What needs to change

• Rename the field method from issues to recent_issues
• Update the prefetch_related key if necessary
• Update any GraphQL queries or frontend code that references issues on a repository node

Acceptance Criteria

• Field is renamed to recent_issues in the node definition
• All consumers of this GraphQL field are updated
• Existing tests pass; new/updated tests cover the renamed field

[miran786]

Hi @arkid15r and @kasya, Could you please assign this to me??

[pat031-prog]

Hi @arkid15r, I'd like to take this on. I'm a full-stack dev (Python, Django, React, TS) looking to contribute to Nest for GSoC 2026 — focused on the NestBot AI assistant project. Can you assign this to me?

[Jpeg-create]

Hi @arkid15r, I'd like to work on this issue as well. I have 2 merged PRs in this repo (#4201, #4207)

[taditharun]

Hii @arkid15r , i did like to work on this issue , i have setup Nest locally in my PC and gone through the contributing guidelines couild you please assign it to me .