{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiejhyk7ht5ut2iixyx4z4wsbjprsetifdflgcmx7otko5d5i2qgqq",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mevpz3utmr72"
  },
  "path": "/t/contributor-responsibility-and-review-cost-in-the-age-of-code-generation/24010#post_7",
  "publishedAt": "2026-02-15T09:48:53.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "kornel:\n\n> If I just submit the groundwork, it gets rejected as a pointless change for the sake of change. However, if I submit refactorings plus a new feature together, I often get told off for changing unnecessary stuff at the same time, and not splitting PRs into small enough pieces.\n\nThis is where I wish GitHub had better handling of commit-by-commit review. I similarly most of the time do two-commit reviews where the first refactors and the second implements.",
  "title": "Contributor Responsibility and Review Cost in the Age of Code Generation"
}