Page MenuHomePhabricator

Remove very old "vsDiff" data from commit update / diff extraction pipeline
ClosedPublic

Authored by epriestley on Apr 11 2019, 1:12 PM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Nov 20, 1:31 AM
Unknown Object (File)
Sat, Nov 16, 1:48 AM
Unknown Object (File)
Tue, Nov 12, 5:09 AM
Unknown Object (File)
Fri, Nov 8, 1:07 PM
Unknown Object (File)
Oct 21 2024, 2:01 PM
Unknown Object (File)
Oct 19 2024, 1:53 AM
Unknown Object (File)
Oct 17 2024, 4:39 AM
Unknown Object (File)
Oct 13 2024, 2:04 PM
Subscribers
None

Details

Summary

Ref T13276. This was introduced in D2586 to power a "trigger audits when the committed change does not match the reviewed change" feature. It was removed without ceremony in D15939. Broadly, rebases mean that this sort of feature can't really work like this and this approach is inherently unreliable; see also T182.

This property no longer has readers, and is unlikely to get any in the future since my planned pathway for "committed code must match reviewed code, modulo an automated rebase" is automating the rebase via "Land Revision", not comparing the diff text.

Remove this to simplify the flow of data here so that things in T13276 can be fixed more easily.

Test Plan

Grepped for vsDiff, no hits.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable