Skip to content

docs(#843): document event_payload for run-to-PR correlation #846

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
fullsend-ai-coder wants to merge 1 commit into
base: main
Choose a base branch
from
+20 −0
Open

docs(#843): document event_payload for run-to-PR correlation #846

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions skills/retro-analysis/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,6 +76,26 @@ gh run view <RUN_ID> --repo "$DISPATCH_REPO" --log 2>&1 \
gh run download <RUN_ID> --repo "$DISPATCH_REPO"
```

### Correlating dispatch-repo runs to source-repo PRs

Dispatch-repo run logs contain an `event_payload` JSON line with fields
that map each run directly to its source-repo PR and commit — no
timestamp heuristics or branch-name matching required.

Key fields in `event_payload`:

- `pull_request.head.sha` — the source-repo commit the run executed against
- `pull_request.number` — the source-repo PR number
- `pull_request.base.ref` — the target branch of the PR

```bash

@fullsend-ai-review fullsend-ai-review Bot Aug 17, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

[low] edge-case

The grep -o 'event_payload.*' command captures from event_payload to end-of-line only. If the event_payload JSON in the log is spread across multiple lines, only the first line would be captured. GitHub Actions structured logs typically use single-line entries, making this unlikely in practice.

Suggested fix: Consider adding a note that the command assumes single-line JSON log entries, or suggest jq for structured extraction if multi-line output is possible.

# Extract event_payload from a dispatch-repo run log
gh run view <RUN_ID> --repo "$DISPATCH_REPO" --log 2>&1 \
| grep -o 'event_payload.*'
```

Use this as the primary method for run-to-PR/commit correlation.

## Exploration strategy

You have a large amount of context to cover. Use subagents to avoid overflowing your main context window.
Expand Down
Loading