feat(code): persist PR URLs to backend & emit file activity events#1434
Open
adboio wants to merge 1 commit into04-01-feat_code_add_attribution_to_pr_body_from_uifrom
Open
Conversation
This was referenced Apr 1, 2026
Contributor
Author
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
fde3cd3 to
b05db93
Compare
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.

Problem
when agents create PRs, we detect the URLs from bash output and store them on the backend
but when created via UI in posthog code, we do no such thing
also, we generally need a better way to correlate local tasks to branches (and therefore PRs)
Changes
when PRs are created via UI, call
updateTaskRunwith the PR URLi accidentally also combined this with the change to emit events on file changes (which helps build a "loose" task<>branch association)
How did you test this?
created PR via UI, verified task in db: