Repository navigation
Conversation
…ry()
getListRepository() is documented to list the issue events of a
repository, but requested /repos/{owner}/{repo}/issues/{id}/comments,
the comments of one issue. Request /repos/{owner}/{repo}/issues/events
and deprecate the $issueId parameter, which that endpoint has no use for.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary of Changes
Issues\Events::getListRepository($owner, $repo, $issueId, $page, $limit)is documented as "List events for a repository", but requested/repos/{owner}/{repo}/issues/{issueId}/comments— the comments of one issue. It now requests/repos/{owner}/{repo}/issues/eventswith paging.The
$issueIdparameter has no meaning for that endpoint. It stays in place (now optional) so$page/$limitkeep their positions, is ignored, and triggers a deprecation when passed (removal in 5.0; addssymfony/deprecation-contracts^2|^3). Behaviour change in 4.x: callers that relied on getting issue comments from this method get issue events now;Issues\Comments::getList()is the method for comments.Testing Instructions
Tests/Package/Issues/EventsTest.php:testGetListRepositoryasserts the events path with paging;testGetListRepositoryWithIssueIdexpects the deprecation. Both fail before the change.Documentation Changes Required
docs/overview.md: short section on the method and the deprecated parameter. The 5.x removal of the parameter follows with the other 5.0 removals.🤖 Generated with Claude Code