Google Git
Sign in
chromium / chromiumos / platform / redaction_tool / refs/heads/firmware-ec-R133-16151.2.B
commit2543a686a5805d8d2e25a4e4f107c778519f4632[log] [tgz]
authorAndrew Moylan <amoylan@google.com>Fri Nov 15 02:35:38 2024
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Nov 18 17:37:09 2024
tree17e70fca148740c52ef1ed0860b8dd9ecf8abb42
parentbebfe56bbc207c45c8dc30a709ce70ca3110d912 [diff]
redaction_tool: NOTREACHED_NORETURN -> NOTREACHED

NOTREACHED is already [[noreturn]] and fatal and can replace
NOTREACHED_NORETURN. See also Chrome-side CL crrev.com/c/5782602.

BUG=b:378997870
TEST=CQ only

Change-Id: I2e41faa803cdd97a63bad0c4587d421ccb098c71
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/redaction_tool/+/6024745
Commit-Queue: Ahmed Fakhry <afakhry@chromium.org>
Auto-Submit: Andrew Moylan <amoylan@google.com>
Tested-by: Andrew Moylan <amoylan@google.com>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
1 file changed
tree: 17e70fca148740c52ef1ed0860b8dd9ecf8abb42
  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