Skip to content

M03 RECON: prove official MCP standard write with branch creation - #5

Merged
GBOGEB merged 1 commit into
mainfrom
recon/qps-official-branch-write
Sep 11, 2026
Merged

GBOGEB merged 1 commit into
mainfrom
recon/qps-official-branch-write

Conversation

@GBOGEB

@GBOGEB GBOGEB commented Sep 11, 2026

Copy link
Copy Markdown
Owner

Mission

M03_GITHUB_MCP_SERVER / P_M03_OFFICIAL_BRANCH_WRITE_01

Objective

Advance from two live read families to one real low-risk standard write mutation through the exact official MCP server.

Controlled mutation

  • exact official source: github/github-mcp-server@7d13a7ad6f2a17f351a6d77ce280c85ae1821f4d;
  • toolset/tool: repos/create_branch;
  • target: GBOGEB/github-mcp-server;
  • source branch: main;
  • created branch: unique probe/m03-official-write-${GITHUB_RUN_ID};
  • no file/content mutation and no QPS semantic change.

FIRST RED discipline

Only recurse on the first observed step: runner -> exact checkout -> build -> schema -> permission/API mutation -> response binding -> receipt.

Authority boundary

GREEN proves one standard GitHub write operation through official MCP transport. It does not prove all write tools, all auth modes, or Governor/DoV semantics. QPS remains the control/evidence plane.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 11, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-09-11T16:43:52.511098Z bffce38 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@GBOGEB
GBOGEB merged commit 3268664 into main Sep 11, 2026
15 of 16 checks passed
@GBOGEB
GBOGEB deleted the recon/qps-official-branch-write branch September 11, 2026 16:42

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: bffce38c7f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +4 to +5
pull_request:
branches: [main]

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Restrict the write probe to trusted pull requests

For pull requests originating from forks (including Dependabot-style fork contexts), GitHub downgrades github.token to read-only despite the requested contents: write permission. Because this workflow runs for every PR targeting main, the later create_branch call against GBOGEB/github-mcp-server will fail for external contributions; gate the job to same-repository PRs or reserve this mutation for workflow_dispatch.

Useful? React with 👍 / 👎.

run: |
set -euo pipefail
SERVER_CMD="$RUNNER_TEMP/github-mcp-server stdio --toolsets=repos"
PROBE_BRANCH="probe/m03-official-write-${GITHUB_RUN_ID}"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Include the run attempt in the probe branch name

When this workflow is rerun, GITHUB_RUN_ID remains unchanged, so any first attempt that reached branch creation leaves this exact ref behind. A rerun—particularly after a later artifact or receipt step failed—then receives an already-exists error from create_branch and can never recover; include GITHUB_RUN_ATTEMPT in the name or make existing-branch handling idempotent.

Useful? React with 👍 / 👎.

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.

1 participant