Repository navigation
M03 RECON: prove official MCP standard write with branch creation - #5
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 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".
| pull_request: | ||
| branches: [main] |
There was a problem hiding this comment.
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}" |
There was a problem hiding this comment.
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 👍 / 👎.
Mission
M03_GITHUB_MCP_SERVER/P_M03_OFFICIAL_BRANCH_WRITE_01Objective
Advance from two live read families to one real low-risk standard write mutation through the exact official MCP server.
Controlled mutation
github/github-mcp-server@7d13a7ad6f2a17f351a6d77ce280c85ae1821f4d;repos/create_branch;GBOGEB/github-mcp-server;main;probe/m03-official-write-${GITHUB_RUN_ID};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.