ATProto Browser

Record data

{
  "uri": "at://did:plc:hwevmowznbiukdf6uk5dwrrq/sh.tangled.repo.issue.comment/3lmmzzsa5pu22",
  "cid": "bafyreibphhs5gi5wlb5lyoexqpvj4hkffwy76cifekbu3pwtt7qm527iom",
  "value": {
    "body": "dropping my thoughts on what i want the PR flow to look like. i want to introduce a turn-based review system, where every \"submission\" is immutable:\n\n- user first \"forks\" a repo, and makes some changes on a branch\n- user then \"submits\" to target repo when ready -- this could be as many commits as they like\n-this creates \"round 1\" of \"PR 1\"\n-the owner can then offer a review on \"round 1\"\n- the user then makes updates to their branch based on feedback\n- at this point, unlike github, the PR is not updated automatically with new contents. the branch should not be used as a working area. - rather, the user can make the changes they want, to address the review, and \"resubmit\" the branch for review\n\nthis creates \"round 2\", with the patchset produced from the same branch\n\"round 2\" may add, delete or rework commits, by means of simply new changes, or performing a rebase on the branch\nreview process continues\nthe things this offers over the standard github model:\n\nreviewers can request that commit history be clean, and even comment on specific commits in the history\nreviewers can use \"range diff\" to tell the difference between submissions, existing flows cannot do this\nfinally, at the point of merge, there will be 3 options as suggested by @shi.gg.",
    "repo": "at://did:plc:hwevmowznbiukdf6uk5dwrrq/sh.tangled.repo/3llmbkfueu522",
    "$type": "sh.tangled.repo.issue.comment",
    "issue": "at://did:plc:hwevmowznbiukdf6uk5dwrrq/sh.tangled.repo.issue/3lmmoy4lhrv22",
    "owner": "did:plc:hwevmowznbiukdf6uk5dwrrq",
    "commentId": 127035,
    "createdAt": "2025-04-12T20:17:48+03:00"
  }
}