Skip to content

Handle Octokit::UnprocessableEntity in GitHub solution syncer PR creation#8609

Merged
iHiD merged 1 commit into
mainfrom
fix/8596
Feb 12, 2026
Merged

Handle Octokit::UnprocessableEntity in GitHub solution syncer PR creation#8609
iHiD merged 1 commit into
mainfrom
fix/8596

Conversation

@iHiD
Copy link
Copy Markdown
Member

@iHiD iHiD commented Feb 12, 2026

Closes #8596

Summary

  • Add Octokit::UnprocessableEntity to the rescue clause in User::GithubSolutionSyncer::CreatePullRequest
  • When GitHub returns a 422 "No commits between branches" error during PR creation, the syncer now silently handles it instead of raising to Sentry
  • This is consistent with the existing handling of Octokit::NotFound and Octokit::Forbidden

Test plan

  • Added test for Octokit::UnprocessableEntity being raised during create_pull_request
  • All 4 CreatePullRequestTest tests pass

🤖 Generated with Claude Code

…tion

When there are no commits between the base and sync branches, GitHub
returns a 422 error. This can happen when the sync process determines
there are changes but the resulting commits don't differ from the base.
Handle this the same way as NotFound and Forbidden — as a permanent
failure that doesn't need retrying.

Closes #8596

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@iHiD iHiD merged commit e093020 into main Feb 12, 2026
41 checks passed
@iHiD iHiD deleted the fix/8596 branch February 12, 2026 17:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant