No code change needed: agent already embeds session URL in PR body - #950
Open
empiricalrun[bot] wants to merge 5 commits into
Open
No code change needed: agent already embeds session URL in PR body#950empiricalrun[bot] wants to merge 5 commits into
empiricalrun[bot] wants to merge 5 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:
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
updatePullRequesthelper togithub.ts+ patched the PR body inmergePrFromSessionbefore merging via the GitHub proxy API. This worked but was flagged as over-engineering (and had a hardcoded/flash/path).Both
updatePullRequestingithub.tsand the session-annotation block inmergePrFromSessionhave 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