{"version":"2.1.238","anchor":"diff-output-says-why-some-hunks-are-withheld-even-when-you-c","canonical_anchor":"diff-output-says-why-some-hunks-are-withheld-even-when-you-c","heading":"Diff output says why some hunks are withheld even when you can read the file","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/diff-output-says-why-some-hunks-are-withheld-even-when-you-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Diff output says why some hunks are withheld even when you can read the file\n\nDiffs now explain that withheld hunks are held by a provenance check stricter than read permissions.\n\n**What**\n\nThe diff tool's `restricted` field now states that withheld hunks are held back by a content-provenance check stricter than read permissions: symlinked and hardlinked files in a worktree are refused here even where reading them is allowed. Statistics for those files stay visible.\n\n**Evidence**\n\n`symlink and hardlinked worktree files are refused here even where read_file serves them`\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}