feat(code): persist PR URLs to backend & emit file activity events#1434
Merged
feat(code): persist PR URLs to backend & emit file activity events#1434
Conversation
This was referenced Apr 1, 2026
Contributor
Author
fde3cd3 to
b05db93
Compare
fea8dfe to
af2751d
Compare
b05db93 to
53f246d
Compare
charlesvien
approved these changes
Apr 2, 2026
53f246d to
1451a1a
Compare
b634fac to
d93a6fb
Compare
1451a1a to
08dc016
Compare
d93a6fb to
4798ef7
Compare
08dc016 to
10ed46e
Compare
23ea7b7 to
9016536
Compare
10ed46e to
de03f96
Compare
9016536 to
fa9a488
Compare
de03f96 to
c6960fc
Compare
c6960fc to
38cd461
Compare
Contributor
Author
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: