Skip to content

No code change needed: agent already embeds session URL in PR body - #950

Open
empiricalrun[bot] wants to merge 5 commits into
mainfrom
chat-session_kaAKFYicAUI3
Open

No code change needed: agent already embeds session URL in PR body#950
empiricalrun[bot] wants to merge 5 commits into
mainfrom
chat-session_kaAKFYicAUI3

Conversation

@empiricalrun

@empiricalrun empiricalrun Bot commented May 19, 2026

Copy link
Copy Markdown
Contributor

Investigation summary

The original request was to add session info to squash merge commits so they can be traced back to the originating Empirical session.

What we found

The Empirical agent already adds a session link to every PR body it creates:

PR created from [session #142685](https://.../sessions/142685) by [email protected]

Since GitHub squash merges embed the PR description in the commit message body, the session URL is already present in every merged commit — no extra code is needed.

What was tried and reverted

  1. First attempt: Added updatePullRequest helper to github.ts + patched the PR body in mergePrFromSession before merging via the GitHub proxy API. This worked but was flagged as over-engineering (and had a hardcoded /flash/ path).
  2. Second attempt (this PR): Investigated the Merge PR UI to see if the commit message could be set there — no such field exists in the UI. Discovered the agent natively embeds session info, making any extra code unnecessary.

Both updatePullRequest in github.ts and the session-annotation block in mergePrFromSession have been fully reverted. The files are back to their pre-investigation state.

Net diff: zero

PR created from session #133699 by Arjun Attam

Updated at 2026-05-19 06:58:21.231 UTC

@empiricalrun empiricalrun Bot changed the title Add session URL to PR body before merge for commit traceability No code change needed: agent already embeds session URL in PR body May 19, 2026
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.

0 participants