Repository navigation
M03 RECON: execute live Actions read through official MCP - #4
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: 109a691e8d
ℹ️ 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".
| echo "response_path=$RESPONSE" >> "$GITHUB_OUTPUT" | ||
|
|
||
| - name: Upload raw public Actions MCP response diagnostic | ||
| uses: actions/upload-artifact@v4 |
There was a problem hiding this comment.
Upload the raw response after validation failures
When the MCP call produces a non-empty error or malformed response, the validation step fails and this upload is skipped by the default success() condition, so the raw diagnostic needed to investigate the first failure is lost. The analogous upload in .github/workflows/qps-official-live-read.yml uses if: always() with if-no-files-found: warn; apply the same pattern here so API and response-validation failures retain their evidence.
Useful? React with 👍 / 👎.
Mission
M03_GITHUB_MCP_SERVER/P_M03_OFFICIAL_ACTIONS_LIVE_READ_02Objective
Advance beyond representation/unit smoke into one real GitHub Actions API read through the exact official MCP server.
Execution path
github/github-mcp-server@7d13a7ad6f2a17f351a6d77ce280c85ae1821f4d;mcpcurl;actionstoolset;actions_listdiscovery and CLI schema;actions_list(method=list_workflow_runs)againstGBOGEB/github-mcp-server/qps-official-live-read.yml;Authority boundary
GREEN proves a real read-only Actions operation through official MCP transport. It does not yet prove write operations, all auth modes, all QPS evidence semantics, or full transport equivalence. QPS remains the control/evidence plane.
FIRST RED
Recurse only on the first observed failure: runner -> exact checkout -> build -> tool discovery -> auth/API call -> response validation -> receipt.
No upstream sync/fast-forward or QPS semantic redesign is included.