{
  "path": "/logues/my-test-logue",
  "site": "https://logue.is/my-test-logue",
  "$type": "site.standard.document",
  "title": "-",
  "content": {
    "$type": "is.logue.content",
    "items": [
      {
        "$type": "is.logue.block.text",
        "plaintext": "Pull requests are the beating heart of GitHub. As engineers, this is where we spend a good portion of our time. And at GitHub’s scale—where pull requests can range from tiny one-line fixes to changes spanning thousands of files and millions of lines—the pull request review experience has to stay fast and responsive."
      },
      {
        "$type": "is.logue.block.text",
        "facets": [
          {
            "$type": "is.logue.richtext.facet",
            "index": {
              "$type": "is.logue.richtext.facet#byteSlice",
              "byteEnd": 73,
              "byteStart": 60
            },
            "features": [
              {
                "$type": "is.logue.richtext.facet#bold"
              }
            ]
          }
        ],
        "plaintext": "We recently shipped the new React-based experience for the Files changed tab (now the default experience for all users). One of our main goals was to ensure a more performant experience across the board, especially for large pull requests. That meant investing in, and consistently prioritizing, the hard problems like optimized rendering, interaction latency, and memory consumption."
      }
    ]
  },
  "publishedAt": "2026-04-09T19:34:51.185Z",
  "textContent": "Pull requests are the beating heart of GitHub. As engineers, this is where we spend a good portion of our time. And at GitHub’s scale—where pull requests can range from tiny one-line fixes to changes spanning thousands of files and millions of lines—the pull request review experience has to stay fast and responsive.\nWe recently shipped the new React-based experience for the **Files changed** tab (now the default experience for all users). One of our main goals was to ensure a more performant experience across the board, especially for large pull requests. That meant investing in, and consistently prioritizing, the hard problems like optimized rendering, interaction latency, and memory consumption."
}