Skip to content

fix(mcp): accept GitHub's 200 answer to a dispatch - #10

Merged
jasp402 merged 1 commit into
mainfrom
claude/project-thread-1lh7zs
Oct 19, 2026
Merged

jasp402 merged 1 commit into
mainfrom
claude/project-thread-1lh7zs

Conversation

@jasp402

@jasp402 jasp402 commented Oct 19, 2026

Copy link
Copy Markdown
Owner

Before: GitHub started the community-render workflow (run 39313403755), but the MCP expected a 204 response, got a 200, and recorded the job as not sent. The user saw "could not be sent", and the job's result was refused.

After: any 2xx response counts as sent. A job that really could not be sent is retried on the next call instead of after 15 minutes.

Tests: 57/57.


Generated by Claude Code

…t job at once

GitHub now answers repository_dispatch with 200, so every job was started
but recorded as not sent.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TXFXQJroZAF74W4gg57vyH
@vercel

vercel Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
hypercodemotion-mcp-service Ready Ready Preview Oct 19, 2026 7:44pm UTC

@jasp402
jasp402 merged commit ee536a6 into main Oct 19, 2026
2 of 3 checks passed

This branch was successfully deployed

1 active deployment
Preview — a3411ae4 Deployed Oct 19, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants