Clone this repo:
  1. 55ec79c redaction_tool: Add LVM UUIDs by Sarthak Kukreti · 3 months ago factory-brya-15684.B main release-R119-15633.B release-R120-15662.B stabilize-15633.44.B stabilize-15642.B stabilize-15654.B stabilize-15677.B
  2. 652894e replace deprecated base::StackVector with absl::InlinedVector by Brett Brotherton · 4 months ago firmware-cr50-prepvt-15608.B release-R118-15604.B stabilize-15588.B stabilize-15604.16.B stabilize-15604.45.B stabilize-15604.56.B stabilize-15610.B
  3. 0d58e7b redaction_tool: Keep source up to date (Perf metrics and crash reports) by Christoph Schlosser · 5 months ago release-R117-15572.B stabilize-15561.B stabilize-15562.B stabilize-15563.B stabilize-15564.B stabilize-15572.16.B stabilize-15572.39.B stabilize-15572.4.B stabilize-15572.50.B stabilize-15572.57.B stabilize-15572.63.B
  4. d0cfa7c redaction_tool: Keep source up to date (Platform specific metrics) by Christoph Schlosser · 5 months ago stabilize-15531.B stabilize-15532.B
  5. c5028d1 redaction_tool: Keep source up to date (prepare for re2 upgrade) by Christoph Schlosser · 6 months ago main-deprecated release-R116-15509.B stabilize-15509.37.B stabilize-15509.63.B stabilize-15509.72.B stabilize-15511.B stabilize-15519.B

redaction_tool: PII Redaction Tool

A redaction_tool redacts PII using a wide set of RegEx expressions.

This code is a mirror of

Changes should be made in chromium code base only and then be upreved here.

How to update the source

To pull in updates from chromium/src, do the following:

  • git remote update
  • git checkout -b main cros/main
  • git merge cros/upstream/main
    • should mostly use the version from main, unless the upstream changes the files to be built.
    • The #include paths should use the version from main (without “components/feedback”). This should be the majority of the merge conflicts.
    • In the commit message of the merge, list the commits from upstream that are merged.
    • If you need to make changes to the merged commits (outside of conflicts), do that work in separate commits. For example, if you need to revert commits, use git revert after committing the merge commit. This preserves the history and makes it clear why a change is being reverted rather than quietly changing it in the merge commit.
    • Check the changes introduced by your merge by doing a diff against the commit before the merge. The difference should be the same as the changes in the upstream.
  • Push the resulting merge commit for review with:
    • git push HEAD:refs/for/main