Validate GitHub pagination cursors in internal/github/list.go

[Jagadeeshftw]

📌 Description

internal/github/list.go handles paginated GitHub API listing (issues, PRs, etc.), but if the cursor/page-link parsing doesn't validate the returned Link header format defensively, a malformed or unexpected response from GitHub could cause an infinite pagination loop or a panic.

🧩 Requirements and context

• Add defensive parsing/validation of the Link header used to find the 'next' page.
• Cap the maximum number of pages followed per call as a safety net against infinite loops.
• Return a typed error on malformed pagination data instead of panicking.

🛠️ Suggested execution

• Review the pagination-following logic in internal/github/list.go.
• Add a max-page-count guard and a parse-failure typed error.
• Add a test with a malformed Link header asserting graceful failure, not a loop/panic.

✅ Acceptance criteria

• Malformed Link headers produce a typed error, not a panic or infinite loop.
• A hard page-count cap exists as defense in depth.
• Existing well-formed pagination continues to work.

🔒 Security notes

Defends against a misbehaving or compromised upstream (GitHub API proxy/cache) causing resource exhaustion via unbounded pagination.

📋 Guidelines

• Minimum 95% test coverage
• Clear documentation
• Timeframe: 96 hours

[Primex-hub]

I will like to take this job

[Jagadeeshftw]

Assigned @Primex-hub to this issue. Please open a PR referencing it with Closes #121 when you are ready. If you need help, join our contributor chat: https://t.me/+vTbe0hOUKrFhNTJl

[Jagadeeshftw]

Unassigning @Primex-hub — this has been assigned for more than 2 days with no PR opened yet. No worries if you're still working on it, just re-comment and we'll happily reassign once you're ready to pick it back up.

[Jagadeeshftw]

Assigned @Primex-hub! Go ahead and open a PR referencing this issue (Closes #121) when ready. t.me/+vTbe0hOUKrFhNTJl