Handle Secondary Rate Limit Errors in CLI

[Copilot]

This PR implements secondary rate limit handling in the GitHub CLI to gracefully handle 403/429 responses with proper retry logic, exponential backoff, and clear error messaging, improving reliability when running multiple concurrent migrations.

Background

Recent GraphQL database rate limiting changes now count Octoshift backend operations against the PAT, causing failures when migrations run in parallel. Previously, the CLI would fail immediately on secondary rate limit errors (HTTP 403/429) without any retry logic, making it brittle in both CI and customer environments.

Key Changes

The implementation makes minimal surgical changes to the GithubClient.SendAsync method:

1. Added IsSecondaryRateLimit method to detect secondary rate limit responses
2. Added HandleSecondaryRateLimit method to implement retry logic with proper header handling
3. Enhanced SendAsync method with retry count parameter and secondary rate limit handling
4. Added comprehensive test coverage for various secondary rate limit scenarios

Closes #1425
Closes https://github.ghe.com/github/octoshift/issues/11153

[github-actions]

Unit Test Results

  1 files    1 suites   10m 25s ⏱️
905 tests 905 ✅ 0 💤 0 ❌
906 runs  906 ✅ 0 💤 0 ❌

Results for commit 514da55.

♻️ This comment has been updated with latest results.

[Copilot]

Pull Request Overview

This PR implements secondary rate limit handling in the GitHub CLI to improve reliability when running concurrent migrations by adding retry logic with exponential backoff for 403/429 HTTP responses.

• Adds detection and handling for secondary rate limits (HTTP 403/429) with automatic retry logic
• Implements exponential backoff strategy when retry headers are not present
• Provides clear warning messages and error handling after maximum retries are reached

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
src/Octoshift/Services/GithubClient.cs	Core implementation of secondary rate limit detection and retry logic with exponential backoff
src/OctoshiftCLI.Tests/Octoshift/Services/GithubClientTests.cs	Comprehensive test coverage for various secondary rate limit scenarios including 429/403 responses and retry behavior
RELEASENOTES.md	User-facing documentation of the new secondary rate limit handling feature

[V1j2t3]

This PR implements secondary rate limit handling in the GitHub CLI to gracefully handle 403/429 responses with proper retry logic, exponential backoff, and clear error messaging, improving reliability when running multiple concurrent migrations.

Background

Recent GraphQL database rate limiting changes now count Octoshift backend operations against the PAT, causing failures when migrations run in parallel. Previously, the CLI would fail immediately on secondary rate limit errors (HTTP 403/429) without any retry logic, making it brittle in both CI and customer environments.

Key Changes

The implementation makes minimal surgical changes to the GithubClient.SendAsync method:

1. Added IsSecondaryRateLimit method to detect secondary rate limit responses
2. Added HandleSecondaryRateLimit method to implement retry logic with proper header handling
3. Enhanced SendAsync method with retry count parameter and secondary rate limit handling
4. Added comprehensive test coverage for various secondary rate limit scenarios

Closes #1425 Closes https://github.ghe.com/github/octoshift/issues/11153

[github-actions]

Package	Line Rate	Branch Rate	Complexity	Health
gei	80%	72%	574	✔
bbs2gh	83%	77%	653	✔
ado2gh	83%	77%	613	✔
Octoshift	87%	77%	1503	✔
Summary	85% (7315 / 8631)	76% (1733 / 2276)	3343	✔