From 8bd3ed37cc498a151331d8111e5933fe23547d35 Mon Sep 17 00:00:00 2001 From: Anirudh Oppiliappan Date: Wed, 16 Apr 2025 23:28:35 +0300 Subject: [PATCH] link atproto record --- pages/blog/pulls.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/pages/blog/pulls.md b/pages/blog/pulls.md index 9b8fa19..a48d2e2 100644 --- a/pages/blog/pulls.md +++ b/pages/blog/pulls.md @@ -13,7 +13,7 @@ authors: - name: Akshay email: akshay@tangled.sh handle: oppili.bsky.social -draft: true +draft: false --- We've spent the last couple of weeks building out a pull @@ -116,8 +116,11 @@ and any potential merge conflicts -- are always based on the latest state of the target branch. And just like earlier, we produce the patch by diffing your -feature branch with the hidden tracking ref and do the whole -atproto record thing. +feature branch with the hidden tracking ref. Also, the entire pull +request is stored as [an atproto record][atproto-record] and updated +each time the patch changes. + +[atproto-record]: https://pdsls.dev/at://did:plc:qfpnj4og54vl56wngdriaxug/sh.tangled.repo.pull/3lmwniim2i722 Neat, now that we have a patch; we can move on the hard part: code review. -- 2.51.2