[sary (saryn17)]

repo_pull_request with action: "get" and includeChangedFiles: true did not pass top or skip to getPullRequestIterationChanges, so callers could not retrieve changes beyond the first page (#1611).

This change forwards the existing top and skip parameters and documents how to request the next page using nextSkip and nextTop from changedFilesSummary. The defaults remain top: 100 and skip: 0.

GitHub issue number

#1611

Associated Risks

• top and skip now apply to get (changed files) as well as list (pull requests). Both descriptions name both actions.
• top is not clamped, so a value above the documented maximum of 2000 reaches the service as written.
• Paging is caller-driven, so iterations[iterations.length - 1] is re-read on every call. Page 2 can land on a newer iteration than page 1 if someone pushes in between. secondComparingIteration is in the summary whenever there is an iteration to compare, so a caller can see that. Iteration pinning is tracked in Expose pull request iteration identity in get_changes #1551.

✅ PR Checklist

• I have read the contribution guidelines
• I have read the code of conduct guidelines
• Title of the pull request is clear and informative.
• 👌 Code hygiene
• 🔭 Telemetry added, updated, or N/A
• 📄 Documentation added, updated, or N/A
• 🛡️ Automated tests added, or N/A

🧪 How did you test it?

Unit tests in test/src/tools/repositories.test.ts cover the default page size, a non-default page size, the continuation fields, both ways the endpoint ends a list, and the absence of hasMore:

• neither top nor skip given: the schema fills in 100 and 0, and both reach getPullRequestIterationChanges
• top: 100, skip: 0 against the 150-file response recorded in repo_pull_request get: includeChangedFiles silently stops at 100 files #1611: fileCount: 100, the first entry is the first file, nextSkip: 100, nextTop: 50
• top: 50, skip: 100, following the REST example for this endpoint: fileCount: 50, the last entry is the 150th file, no nextSkip or nextTop
• an explicit nextSkip: 0 and nextTop: 0 is surfaced as the API sent it
• the existing includeChangedFiles test asserts the two added arguments

21 suites, 1298 tests passing. npm run validate-tools, eslint and prettier --check clean.

[Codecov Comments Bot (codecov-commenter)]

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (main@b271bec). Learn more about missing BASE report.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1615   +/-   ##
=======================================
  Coverage        ?   99.91%           
=======================================
  Files           ?       23           
  Lines           ?     2240           
  Branches        ?      692           
=======================================
  Hits            ?     2238           
  Misses          ?        0           
  Partials        ?        2           

Flag	Coverage Δ
unittests	99.91% <100.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.