Google Git
Sign in
chromium/chromiumos/platform/redaction_tool/refs/heads/release-R147-16610.B
commit
f6c1f87e652902ddc2bad86ac7379f731c9f0fc8
[log]
author
Jeff Lin <[email protected]>
Fri Jan 23 14:17:06 2026
committer
Chromeos LUCI <[email protected]>
Tue Jan 27 01:10:58 2026
tree
0bd0037ee23a0cc11002adcbe3020eef19ab294b
parent
549cb26169ad4f6e8bc9dfcbd9687cd7445dfc50 [diff]
redaction_tool: Migrate base::Contains() to .contains()

base::Contains() is being deprecated by libchrome. This CL changes the
usages of it in redaction_tool to either the native member function
.contains() for associative containers or std::ranges::contains for
sequences.

BUG=b:477205087
TEST=cq

Change-Id: Id75ade905484db42a441489ea640663789e70056
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/redaction_tool/+/7509433
Auto-Submit: Jeff Lin <[email protected]>
Tested-by: Jeff Lin <[email protected]>
Reviewed-by: Chris Mullins <[email protected]>
Commit-Queue: Chris Mullins <[email protected]>
1 file changed
tree: 0bd0037ee23a0cc11002adcbe3020eef19ab294b
  1. BUILD.gn
  2. DIR_METADATA
  3. ip_address.cc
  4. ip_address.h
  5. libmetrics_metrics_recorder.cc
  6. libmetrics_metrics_recorder.h
  7. libmetrics_metrics_tester.cc
  8. libmetrics_metrics_tester.h
  9. metrics_tester.h
  10. OWNERS
  11. pii_types.h
  12. PRESUBMIT.cfg
  13. README.md
  14. redaction_tool.cc
  15. redaction_tool.h
  16. redaction_tool_metrics_recorder.h
  17. redaction_tool_unittest.cc
  18. url_canon.h
  19. url_canon_internal.cc
  20. url_canon_internal.h
  21. url_canon_ip.cc
  22. url_canon_ip.h
  23. url_canon_stdstring.cc
  24. url_canon_stdstring.h
  25. url_parse.h
  26. validation.cc
  27. validation.h
README.md

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