Clone this repo:
  1. bebfe56 Remove zentaro@chromium.org from OWNERS by Owners Cleanup · 7 weeks ago factory-nissa-16077.B firmware-R131-16062.B firmware-brox-16080.B firmware-ec-R131-16063.2.B main release-R131-16063.B stabilize-16055.B stabilize-starline-16056.B
  2. 2d523ac Replace base::StringPiece with std::string_view by Ryo Hashimoto · 3 months ago firmware-R129-16001.B firmware-R130-16032.B firmware-ti50-mp-15980.B firmware-ti50-prepvt-15974.B release-R129-16002.B release-R130-16033.B stabilize-16002.44.B stabilize-16002.51.B stabilize-16033.43.B
  3. c54d719 redaction_tool: keeping the source up-to-date (memory dumps) by Donna Dionne · 9 months ago factory-geralt-15840.B firmware-R126-15885.B firmware-R127-15916.B firmware-R128-15963.B firmware-android-15949.B firmware-geralt-15842.B firmware-hps-15892.B release-R124-15823.B release-R125-15853.B release-R126-15886.B release-R127-15917.B release-R128-15964.B stabilize-15793.B stabilize-15823.40.B stabilize-15828.B stabilize-15855.B stabilize-15857.B stabilize-15886.46.B stabilize-15886.63.B stabilize-15886.66.B stabilize-15888.B stabilize-15905.B stabilize-15917.61.B stabilize-15917.65.B stabilize-15926.B stabilize-15964.20.B stabilize-15964.42.B stabilize-15964.9.B stabilize-hps-15890.B stabilize-quickfix-15823.44.B stabilize-quickfix-15886.43.B
  4. 8410793 Update team email in DIR_METADATA by Ian Barkley-Yeung · 9 months ago release-R123-15786.B stabilize-15786.48.B stabilize-15786.58.B stabilize-quickfix-15786.49.B
  5. 8b48dc0 redaction_tool: Remove debug logging by Ian Barkley-Yeung · 9 months ago

redaction_tool: PII Redaction Tool

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

This code is a mirror of https://source.chromium.org/chromium/chromium/src/+/main:components/feedback/redaction_tool/

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
    • BUILD.gn 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