Closed cstroe closed 8 years ago
It turns out that NodeHeaderChange didn't properly respect the revision number when modifying a node, so if the same node matched across revisions, all were changed. Fix that, and get better coverage.
It turns out that NodeHeaderChange didn't properly respect the revision number when modifying a node, so if the same node matched across revisions, all were changed. Fix that, and get better coverage.