Google Git
Sign in
chromium / chromiumos / platform / redaction_tool / refs/heads/stabilize-quickfix-15786.49.B
commit84107932fbd44e3a5135979afdfe5460cb8a9700[log] [tgz]
authorIan Barkley-Yeung <iby@chromium.org>Thu Feb 08 22:17:20 2024
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Feb 09 22:13:22 2024
treef487b0e886eef09c1fe927bef4ff37db6e89f385
parent8b48dc03739d9bebaca465fc52b248d3caf16e83 [diff]
Update team email in DIR_METADATA

Cros-telemetry is being folded into chromeos-data-eng. Update
DIR_METADATA appropriately.

BUG=b:324495306
TEST=None

Change-Id: Id06fa8101b9e77a750f2b297f470fb33d2bd5df8
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/redaction_tool/+/5280798
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Auto-Submit: Ian Barkley-Yeung <iby@chromium.org>
Reviewed-by: Miriam Zimmerman <mutexlox@chromium.org>
Commit-Queue: Miriam Zimmerman <mutexlox@chromium.org>
Tested-by: Ian Barkley-Yeung <iby@chromium.org>
1 file changed
tree: f487b0e886eef09c1fe927bef4ff37db6e89f385
  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